38 patterns, 16 systems built from them

Foundations What one request actually does, and where its time goes.

Traffic Deciding what gets in, and spreading what does.

Caching Keeping answers closer than the thing that produced them.

Storage Where the data lives, and what it costs to find or move it.

Messaging Handing off work, and surviving what goes wrong with it.

Coordination Several machines agreeing on one answer.

Reliability Failing in ways that stay contained.

Systems built from those patterns

System design, drawn

38 patterns and 16 systems, drawn as isometric line art and played out one step at a time. Packets travel the wires, parts light up, and the state under each label changes as it goes. Yellow means active right now.

Start readingor start from a whole system

How a request travels

If you want one route through it

10 patterns that touch every topic, ordered so nothing arrives before the thing it assumes. Worked out from what each pattern declares, not hand-picked.

  1. 1How a request travels
  2. 2Latency and throughput
  3. 3Stateless services
  4. 4Cache-aside
  5. 5Sharding
  6. 6Publish / subscribe
  7. 7Optimistic locking
  8. 8Heartbeats
  9. 9Bigger or more
  10. 10Load balancing

Patterns

Single mechanisms, grouped by what they are about. 18 of 38 assume nothing at all, so most of this can be read in any order. The rest say what they expect you to have seen.

  1. FoundationsWhat one request actually does, and where its time goes.How a request travelsLatency and throughputStateless servicesBigger or more
  2. TrafficDeciding what gets in, and spreading what does.Rate limiterLoad balancingLoad sheddingAPI gatewayAutoscaling
  3. CachingKeeping answers closer than the thing that produced them.Cache-asideBloom filterContent delivery network
  4. StorageWhere the data lives, and what it costs to find or move it.Connection poolingStoring passwordsRead replicasShardingWrite-ahead logDatabase indexConsistency models
  5. MessagingHanding off work, and surviving what goes wrong with it.Publish / subscribeIdempotency keysEvent streamingOutbox patternFan-out on writeDead-letter queueChange data captureBackpressure
  6. CoordinationSeveral machines agreeing on one answer.Optimistic lockingQuorum reads and writesSagaDistributed lockLeader electionConsistent hashing
  7. ReliabilityFailing in ways that stay contained.Timeouts and retriesHeartbeatsAuto-waitingCircuit breakerBulkhead