System design, drawn

7 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

Connection pooling

Use it whenever many short requests hit a database. Size the pool to what the database can take, not to your traffic.

Assumes nothing. You can start here.