<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Bugpit]]></title><description><![CDATA[Bugpit]]></description><link>https://bugpit.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6aff4ba1bfa6af59fb6e4448/3aade071-9564-4efa-8b85-b0c97ff46b09.png</url><title>Bugpit</title><link>https://bugpit.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 14:40:28 GMT</lastBuildDate><atom:link href="https://bugpit.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Diagrams never crash, so I built a game where your system design does]]></title><description><![CDATA[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…]]></description><link>https://bugpit.hashnode.dev/diagrams-never-crash-so-i-built-a-game-where-your-system-design-does</link><guid isPermaLink="true">https://bugpit.hashnode.dev/diagrams-never-crash-so-i-built-a-game-where-your-system-design-does</guid><category><![CDATA[System Design]]></category><category><![CDATA[webdev]]></category><category><![CDATA[GameDev]]></category><category><![CDATA[side project]]></category><dc:creator><![CDATA[Umar Shaikh]]></dc:creator><pubDate>Thu, 19 Nov 2026 19:24:12 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6aff4ba1bfa6af59fb6e4448/ad2f7f7d-c19e-4074-877a-358d8993620b.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>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.</p>
<p>So I built <strong>Bugpit</strong>, a game where you build a backend from blocks, send it traffic, and watch it break. No code needed.</p>
<h2>How it works</h2>
<ol>
<li>You get a scenario: how much traffic, how much of it is writes, and what the system has to hold up to.</li>
<li>You drag in servers, load balancers, caches, queues and databases, and wire them together.</li>
<li>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.</li>
</ol>
<h2>One example: the write wall</h2>
<p>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.</p>
<table>
<thead>
<tr>
<th>Design</th>
<th>Requests failed</th>
<th>Slowest 1%</th>
</tr>
</thead>
<tbody><tr>
<td>One big database, a cache and a read replica</td>
<td>22.6%</td>
<td>over 12 seconds</td>
</tr>
<tr>
<td>The same, with the database split into 4 shards</td>
<td>0%</td>
<td>84 ms</td>
</tr>
</tbody></table>
<p>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.</p>
<h2>What's in it</h2>
<ul>
<li><strong>34 free levels</strong>, from your first users to running across the world</li>
<li><strong>Real app levels</strong> 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</li>
<li><strong>Timed interview rounds</strong> with a hidden checklist, like a real system design interview</li>
<li><strong>Crash a server on purpose</strong>, or follow one request from start to finish to see where the time goes</li>
</ul>
<p>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.</p>
<h2>Try it</h2>
<p>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.</p>
<p>👉 <a href="https://bugpit.vercel.app">https://bugpit.vercel.app</a></p>
<p>It's built with React, TypeScript, Vite and Tailwind, and the simulator is a plain TypeScript package with no UI in it.</p>
<p>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?</p>
]]></content:encoded></item></channel></rss>