LabsPartly open
Build it, break it, see the result
Reading tells you how a system should behave. A lab lets you find out. Pick a kind and a topic.
The point where waiting explodes (the utilisation knee)
Push load into one app tier and watch p99 climb once it passes the knee.System Design ideasOpen labThree layers for 10,000 requests a second (a three-tier design)
Size Daftar's load balancer (the front door that spreads traffic), app machines and database for exam week, then make it survive losing a zone (one data centre).System Design ideasOpen labWasla's redirects: answers kept in memory (cache-aside)
Put a cache in front of Wasla's links store so 100,000 redirects a second never reach the database.System Design ideasOpen lab
How a visual lab works
Build
Add parts from the list, link them and set their size. Switch between plain names and real AWS names at any time.Choose what to break
Open a part and press Break it. That only arms the failure. Nothing changes until you run.Press Run
The design plays through every scenario: normal traffic, the peak, and each failure.Read the checks
Every test case passes or fails on the board, with the number it measured and why. Fix one thing and run again.