https://yashsachdeva.com/categories/architecture/ Recent content in Architecture on Tech Blog Hugo -- gohugo.io en © 2026 Yash Sachdeva Wed, 25 Mar 2026 22:04:33 +0530 https://yashsachdeva.com/posts/the-anatomy-of-a-distributed-message-broker/ Wed, 25 Mar 2026 22:04:33 +0530 https://yashsachdeva.com/posts/the-anatomy-of-a-distributed-message-broker/ <h2 class="relative group">Introduction <div id="introduction" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#introduction" aria-label="Anchor">#</a> </span> </h2> <p>Distributed message brokers are the backbone of modern microservices architectures, enabling asynchronous communication, decoupling services, and providing a reliable way to handle data streams at scale.</p> https://yashsachdeva.com/posts/rate-limiters/ Tue, 24 Mar 2026 20:49:12 +0530 https://yashsachdeva.com/posts/rate-limiters/ <h2 class="relative group">Life Without a Rate Limiter <div id="life-without-a-rate-limiter" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#life-without-a-rate-limiter" aria-label="Anchor">#</a> </span> </h2> <p>Imagine a public web API that allows clients to fetch user data without any rate limiting. Under normal conditions this might work, but during traffic spikes or abuse (e.g., bots or scrapers) the backend can be overwhelmed, leading to resource exhaustion, cascading failures, and poor availability for legitimate users. Without any form of control, a single noisy neighbor can starve others, increase infrastructure costs, and make it difficult to meet SLAs.</p> https://yashsachdeva.com/posts/system-design-the-path-to-api-gateway/ Sun, 08 Mar 2026 11:34:00 +0530 https://yashsachdeva.com/posts/system-design-the-path-to-api-gateway/ <div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"> Every great architecture starts simple. But as we scale from a single monolith to a swarm of microservices, we hit a wall that only one pattern can break: the <strong>API Gateway</strong>. </div> <h2 class="relative group">Phase 1: The Blissful Monolith <div id="phase-1-the-blissful-monolith" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#phase-1-the-blissful-monolith" aria-label="Anchor">#</a> </span> </h2> <p><em>You have one server, one database, and one endpoint. Everything is easy:</em></p>