<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Monolith on Tech Blog</title>
    <link>https://yashsachdeva.com/tags/monolith/</link>
    <description>Recent content in Monolith on Tech Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Yash Sachdeva</copyright>
    <lastBuildDate>Sun, 08 Mar 2026 11:34:00 +0530</lastBuildDate><atom:link href="https://yashsachdeva.com/tags/monolith/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>System Design: The Path to API Gateway</title>
      <link>https://yashsachdeva.com/posts/system-design-the-path-to-api-gateway/</link>
      <pubDate>Sun, 08 Mar 2026 11:34:00 +0530</pubDate>
      
      <guid>https://yashsachdeva.com/posts/system-design-the-path-to-api-gateway/</guid>
      <description>&lt;div class=&#34;lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl&#34;&gt;&#xA;  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 &lt;strong&gt;API Gateway&lt;/strong&gt;.&#xA;&lt;/div&gt;&#xA;&#xA;&#xA;&lt;h2 class=&#34;relative group&#34;&gt;Phase 1: The Blissful Monolith&#xA;    &lt;div id=&#34;phase-1-the-blissful-monolith&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#phase-1-the-blissful-monolith&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;em&gt;You have one server, one database, and one endpoint. Everything is easy:&lt;/em&gt;&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
