The latest articles on DEV Community by ALIBI Ghazi (@ghazialibi). https://dev.to/ghazialibi https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1078415%2F89474500-aa0b-464a-802d-2db82b4ee880.jpg https://dev.to/ghazialibi en ALIBI Ghazi Wed, 14 Oct 2026 22:15:42 +0000 https://dev.to/ghazialibi/why-i-built-an-interactive-sandbox-to-learn-distributed-systems-5g94 https://dev.to/ghazialibi/why-i-built-an-interactive-sandbox-to-learn-distributed-systems-5g94 <p>When you first start studying system design and distributed systems, almost everything is taught through static boxes and arrows. </p> <p>Someone draws a Load Balancer, an App Server, a Redis Cache, and a Database, and says: <em>"Put a cache in front of the database to handle read traffic, and add retries for fault tolerance."</em></p> <p>On paper, it makes total sense. In practice, systems behave in weird, non-linear ways under load:</p> <ul> <li>What happens when your 92% cache hit rate drops for 30 seconds?</li> <li>What happens when a caller times out and retries, while the downstream service keeps processing the abandoned request anyway?</li> <li>How quickly do queues explode once traffic crosses steady-state capacity?</li> </ul> <p>As I started diving deeper into caching, replication, message queues, and fault tolerance, I realized I couldn't really internalize these concepts just by reading about them. I needed to experiment with them.</p> <p>That's why I started building <strong><a href="https://shardcraft.dev/" rel="noopener noreferrer">ShardCraft</a></strong>.</p> <h2> Turning Theory into Interactive Labs </h2> <p>My goal with ShardCraft is to take complex engineering concepts and turn them into interactive simulations where you can actually see how systems behave under load, failure, and growth.</p> <p>Even building the simplified mathematical models for the site has taught me a ton—having to think through Poisson request arrivals, exponential service-time tails, retry backoff/jitter, and the difference between async slot-freeing vs. thread-per-request blocking.</p> <h2> Learning in Public (Mistakes Included) </h2> <p>I'm definitely not claiming to be a distributed systems expert. I'm building this to learn, ask questions, test my assumptions, and share what I discover along the way. </p> <p>Through this series and on the site, I'll be sharing:</p> <ol> <li> <strong>Deep-dive explanations</strong> into how real systems scale and fail</li> <li> <strong>Interactive labs</strong> where you can break architectures in your browser</li> <li> <strong>Corrections &amp; iterations</strong>—the things I modeled wrong at first before figuring them out</li> </ol> <h2> Come Break Some Systems With Me </h2> <p>Whether you're just starting out with system design or you've been firefighting production incidents for years, I'd love to learn with you (and from you!).</p> <p>👉 <strong>Explore the guides and interactive labs here:</strong> <a href="https://shardcraft.dev/" rel="noopener noreferrer">shardcraft.dev</a></p> <p>If you take a look at the simulation notes or labs, let me know what you think—or drop a comment below on what distributed systems topic you'd love to see simulated next! 🚀</p> distributedsystems systemdesign opensource architecture