Diagrams never crash, so I built a game where your system design does
I kept reading about load balancers, caches and sharding, then forgetting all of it a week later. A diagram never fails, so you never find out why any of it matters. So I built Bugpit, a game where you build a backend f
I kept reading about load balancers, caches and sharding, then forgetting all of it a week later. A diagram never fails, so you never find out why any of it matters.
So I built Bugpit, a game where you build a backend from blocks, send it traffic, and watch it break. No code needed.
How it works
- You get a scenario: how much traffic, how much of it is writes, and what the system has to hold up to.
- You drag in servers, load balancers, caches, queues and databases, and wire them together.
- You run it. Every part has a real capacity, so the simulator shows you what overloads, how many requests fail, how slow the slowest 1% gets, and what it costs per month at real cloud prices.
One example: the write wall
Level 9 sends 20,000 requests a second, and 40% of them are writes. That is 8,000 writes a second, and the biggest database only takes 4,800.
| Design | Requests failed | Slowest 1% |
|---|---|---|
| One big database, a cache and a read replica | 22.6% | over 12 seconds |
| The same, with the database split into 4 shards | 0% | 84 ms |
Read replicas don't help here, because every copy still has to take every write, and a bigger machine stops helping once you hit the largest size. That is the wall sharding exists for. The bill goes up too, which is the other half of the lesson: sharding is often the most expensive line in a design, so teams put it off as long as they can.
What's in it
- 34 free levels, from your first users to running across the world
- Real app levels built on numbers the companies made public: Netflix, Amazon Prime Day, Flipkart's sale, Swiggy, Instagram, ChatGPT, GTA VI launch night, Fortnite at 3.4 million, Hotstar at 25 million and UPI's payments
- Timed interview rounds with a hidden checklist, like a real system design interview
- Crash a server on purpose, or follow one request from start to finish to see where the time goes
Prices and delays come from named sources, and anything without a source is marked as an estimate. It is a simulation, not a load test, and the real app levels are lessons, not copies of those companies' systems. I'm not connected to any of them.
Try it
The first levels open without an account. A free account opens all 34 free levels, plus the Netflix level and one interview round. The other real app levels and interview rounds are part of Bugpit Pro.
It's built with React, TypeScript, Vite and Tailwind, and the simulator is a plain TypeScript package with no UI in it.
I'd love feedback on two things: where did you get stuck or lost, and if you work on real systems, which numbers look wrong to you?
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.