System design, drawn

14 of 38Messaging

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

Idempotency keys

Use them on any write a client might retry. The client supplies a key, the server does the work once, and every retry gets the same answer back.

Assumes nothing. You can start here.