https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/Recent content in Scaling & Performance on An observer's logHugoenhttps://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/leader-follower-replication/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/leader-follower-replication/<p>🔴 P0 &mdash; <em>the default replication strategy for most production databases</em></p>https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/leaderless-replication/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/leaderless-replication/<p>🟠 P1 &mdash; <em>Dynamo-style replication; no single leader, quorum-based</em></p>https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/sharding-strategies/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/sharding-strategies/<p>🔴 P0 &mdash; <em>how to split data across multiple databases when one isn&rsquo;t enough</em></p>https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/consistent-hashing/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/consistent-hashing/<p>🔴 P0 &mdash; <em>minimises data movement when nodes are added or removed</em></p>https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/cache-patterns/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/cache-patterns/<p>🔴 P0 &mdash; <em>the primary tool for read scaling; multiple patterns with different consistency guarantees</em></p>https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/cache-invalidation/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/cache-invalidation/<p>🔴 P0 &mdash; <em>&ldquo;There are only two hard things in CS: cache invalidation and naming things&rdquo;</em></p>https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/rate-limiting-and-backpressure/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/rate-limiting-and-backpressure/<p>🔴 P0 &mdash; <em>definitely Stripe territory; protecting services from overload</em></p>https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/load-balancing/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/load-balancing/<p>🟠 P1 &mdash; <em>distributing traffic across service instances</em></p>https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/batch-and-stream-processing/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/scaling-and-performance/batch-and-stream-processing/<p>🟠 P1 &mdash; <em>two paradigms for processing large volumes of data</em></p>