Challenges
Hit the targets.
Each challenge gives you traffic, a latency goal and a budget. Some designs came from an AI and are broken. Progress is saved on this device.
- 1
Launch day
Your recipe app just got featured. Traffic is 1,000 requests per second, mostly people browsing recipes. One server is melting.Start → - 2
The read-heavy feed
A news feed with 5,000 requests per second. 95% are reads of the same popular stories. Adding app servers alone is not saving the database.Start → - 3
The AI architect's design
An AI assistant designed this for a ticket-booking site at 3,600 requests per second and called it "production ready". It throws errors at peak. Find the bottleneck and fix it without blowing the budget.Start → - 4
Image flood
A photo-sharing site at 8,000 requests per second. 60% of requests are images and scripts that never change. Your app servers spend most of their time sending files.Start → - 5
The overbuilt AI design
An AI suggested this for an internal dashboard with 600 requests per second. It works, but it costs far more than the team’s budget. Cut cost while keeping it healthy.Start →