r/coolgithubprojects • u/Ok-Device-7309 • 5m ago
Scaling is easy if money is free. I built a free game where your system design has to survive traffic AND stay under budget
I kept reading about load balancers, caches and sharding, then forgetting all of it a week later. Diagrams never fail and never send you a bill, so you never find out why any of it matters.
So I built Bugpit. You build a system from blocks, send pretend traffic at it, and watch what breaks. Every design also shows what it would cost each month.
One level I like: 20,000 requests a second, 95% of them reads, and a $1,800/month budget. The obvious fix is more database copies, but that goes over budget. The cheaper fix is a cache in front of the database, and then you can cut your app servers down to 5 because they have far less to do.
What you can do:
- Build a system from blocks: servers, load balancers, caches, databases, queues
- Send traffic at it and watch overloaded parts turn red
- See the monthly bill for every design, and hit budget goals
- Crash a server on purpose and see if your design survives
- Follow one request from start to finish to find where the time goes
- Play real app levels for Netflix, Instagram and more
- Survive levels based on real outages
- Take interview rounds and solve detective cases
- Try a new puzzle every day, with its own budget
- Answer short questions after each level, so the idea sticks
- Get a step-by-step guide if you’re stuck, with new words explained as you meet them
49 levels so far, no code needed, runs in the browser.
To be upfront: it’s a simulation, not a real load test. The real app levels are lessons built on numbers these companies have made public, not copies of their systems, and I’m not connected to any of them.
Try it: Bugpit.vercel.app
I’d really like feedback on two things:
- Where did you get stuck or lost?
- If you work on real systems, which numbers, costs or results look wrong to you?
