Design Lab
Build a system from components, send traffic through it, and see what breaks first.
Illustrative model: a simplified simulation to build intuition, not a prediction of a real system.
Challenges
- First deployA small shop gets 300 requests a second, mostly reads. The starter design already works: keep it cheap and fast.
- Go viralTraffic jumps to 5,000 requests a second. One app server cannot cope. Stay under budget without errors.
- Write stormA flash sale: 2,000 requests a second and half of them are writes. The database can only apply so many writes. For a short burst a backlog is fine, but shoppers must not see errors.
- Global launch20,000 requests a second, 95% reads, 5% writes. Mostly the same popular pages. Keep the bill under control.
- Bot floodReal shoppers send 1,500 requests a second, but a bot network adds 8,000 junk requests on top. Junk uses up capacity everywhere it goes and is never served. Stop it early instead of buying capacity for it.
- Hot tableAn order system takes 3,000 requests a second and 60% of them are writes. One database primary applies 750 writes a second, and a queue only delays the problem: the writes never stop, so no backlog is allowed. Split the data.
- Launch day12,000 real requests a second, 15% of them writes, and 15,000 junk requests a second from bots. Everything above, at once, without a backlog and within budget.
Free play
New free design