System Design 101
You know how to build a feature. Now see how requests, data, traffic and failures shape the whole system.
Your path
Nine short lessons. Start with one web request and build toward distributed system trade-offs.
Your progress is saved on this device. No account required.
How a web request travels
Start hereFollow one request from the browser to the database and back.
Back-of-the-envelope estimation
Turn users and traffic into the rough numbers a design needs.
Load balancing
Spread traffic across servers and survive a machine going down.
Caching strategies
Keep hot data close and stop repeated reads from melting the DB.
CDN & edge caching
Move static content closer to users and away from your origin.
Replication & read scaling
Use copies of data for read scale and failover.
Message queues & event streams
Move slow work off the request path and absorb traffic spikes.
Consistency, CAP & trade-offs
Choose what stays correct and what stays available during failure.
Sharding & partitioning
Split data only when one machine is no longer enough.