<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Microservices on Ansh Wasan</title>
    <link>/tags/microservices/</link>
    <description>Recent content in Microservices on Ansh Wasan</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© {year}</copyright>
    <lastBuildDate>Wed, 14 Jan 2026 21:31:26 +0530</lastBuildDate>
    <atom:link href="/tags/microservices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding Microservices Architecture: From Monolith to Microservices</title>
      <link>/blog/understanding-microservices-architecture/</link>
      <pubDate>Fri, 20 Dec 2024 00:00:00 +0530</pubDate>
      <guid>/blog/understanding-microservices-architecture/</guid>
      <description>Microservices have become a buzzword in backend development. But what exactly are they, and when should you use them? Let&amp;rsquo;s break it down.&#xA;Monolith vs Microservices Monolithic Architecture In a monolith, all components are part of a single, unified codebase:&#xA;┌─────────────────────────────────────┐ │ MONOLITHIC APP │ ├─────────────────────────────────────┤ │ User Service │ Order Service │ │ Payment │ Notification │ │ Inventory │ Analytics │ ├─────────────────────────────────────┤ │ Single Database │ └─────────────────────────────────────┘ Pros:</description>
    </item>
  </channel>
</rss>
