System design, drawn

9 of 38Storage

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

Read replicas

Use them when reads outnumber writes and the data can be a moment behind. All writes stay on one leader, so there is nothing to merge.

Assumes nothing. You can start here.