<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Pratap Vhatkar</title>
    <description>The latest articles on DEV Community by Pratap Vhatkar (@pratapvhatkar).</description>
    <link>https://dev.to/pratapvhatkar</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1135846%2F56689982-0e6d-4ba1-8809-7fb9e1f8be66.png</url>
      <title>DEV Community: Pratap Vhatkar</title>
      <link>https://dev.to/pratapvhatkar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pratapvhatkar"/>
    <language>en</language>
    <item>
      <title>I built a System Design Simulator – drag, simulate, and break your own architectures in minutes</title>
      <dc:creator>Pratap Vhatkar</dc:creator>
      <pubDate>Tue, 10 Mar 2026 09:06:37 +0000</pubDate>
      <link>https://dev.to/pratapvhatkar/i-built-a-system-design-simulator-drag-simulate-and-break-your-own-architectures-in-minutes-1jl0</link>
      <guid>https://dev.to/pratapvhatkar/i-built-a-system-design-simulator-drag-simulate-and-break-your-own-architectures-in-minutes-1jl0</guid>
      <description>&lt;p&gt;Hey folks,&lt;/p&gt;

&lt;p&gt;I’ve been hacking on a side project: a web-based “System Design Simulator.” It’s like a whiteboard, but you can actually press play and watch your architecture behave (or fail).&lt;/p&gt;

&lt;p&gt;What you can do:&lt;/p&gt;

&lt;p&gt;Drag-and-drop common pieces: load balancer, API gateway, caches, DBs, queues, even some AI bits.&lt;br&gt;
Hit “Start Simulation” to see latency, error rate, throughput, cache hit rate in real time.&lt;br&gt;
Flip chaos switches: traffic spikes, cache-miss storms, network partitions, component crashes.&lt;br&gt;
Share &amp;amp; remix: every design gets a short link; anyone can fork it and improve.&lt;br&gt;
Built-in hints: it tells you if you forgot an entry point or storage.&lt;br&gt;
Why I made it:&lt;/p&gt;

&lt;p&gt;Diagrams don’t fail; systems do. I wanted a fast way to feel trade-offs without spinning up infra.&lt;br&gt;
For interviews and design reviews, it’s nice to ask “what if the cache dies?” and just click a button.&lt;br&gt;
Try it here: "&lt;a href="https://paperdraw.dev/" rel="noopener noreferrer"&gt;https://paperdraw.dev/&lt;/a&gt;"&lt;/p&gt;

&lt;p&gt;Quick start: drop Load Balancer → App Server → Cache → DB, press play, then trigger a cache-miss storm.&lt;/p&gt;

&lt;p&gt;Would love feedback:&lt;/p&gt;

&lt;p&gt;What metrics or failure modes would you add?&lt;br&gt;
Is the start/stop flow obvious enough?&lt;br&gt;
Any presets you want (payments, chat, ingestion)?&lt;br&gt;
Should I add “export GIF of the run” for sharing?&lt;br&gt;
Thanks for taking a look—happy to fix bugs or add features if you ping me.&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>showdev</category>
      <category>sideprojects</category>
      <category>systemdesign</category>
    </item>
  </channel>
</rss>
