System design, drawn

36 of 38Reliability

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

Bulkhead

Use it when one slow dependency can eat a resource everything else shares. Give each dependency its own pool, so a failure stays in one compartment.

AssumesConnection pooling