Scaling

🟠 P1 — two paradigms for processing large volumes of data

🟠 P1 — distributing traffic across service instances

🔴 P0 — definitely Stripe territory; protecting services from overload

🔴 P0 — “There are only two hard things in CS: cache invalidation and naming things”

🔴 P0 — the primary tool for read scaling; multiple patterns with different consistency guarantees

🔴 P0 — minimises data movement when nodes are added or removed

🔴 P0 — how to split data across multiple databases when one isn’t enough

🟠 P1 — Dynamo-style replication; no single leader, quorum-based

🔴 P0 — the default replication strategy for most production databases