System design, drawn

31 of 38Coordination

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

Saga

Use it when one business action spans services that each own their own database. There is no transaction to roll back, so every step needs an undo.

AssumesIdempotency keys