<?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 Kuldeep Pisda</title><link>https://kdpisda.in/tag/microservices/</link><description>Recent content in microservices on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 15 Dec 2025 13:54:32 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/microservices/index.xml" rel="self" type="application/rss+xml"/><item><title>Navigating the Labyrinth: A Practical Guide to Distributed Systems Design Patterns</title><link>https://kdpisda.in/navigating-the-labyrinth-a-practical-guide-to-distributed-systems-design-patterns/</link><pubDate>Mon, 15 Dec 2025 13:54:32 +0530</pubDate><guid>https://kdpisda.in/navigating-the-labyrinth-a-practical-guide-to-distributed-systems-design-patterns/</guid><description>&lt;p&gt;Distributed systems design patterns are the established, reusable solutions to the messy, real world problems you hit when an application grows beyond a single machine. Think of them less as abstract theory and more as &lt;strong&gt;battle tested blueprints&lt;/strong&gt; for building systems that can handle scale and chaos without falling over.&lt;/p&gt;
&lt;h2 id="when-your-monolith-starts-to-groan"&gt;When Your Monolith Starts to Groan&lt;a class="heading-anchor" href="#when-your-monolith-starts-to-groan" aria-hidden="true" tabindex="-1"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;We have all been there. It starts with small things. An API endpoint that is a few hundred milliseconds too slow. A database table lock that freezes up a key user workflow.&lt;/p&gt;</description></item><item><title>10 Real World Event Driven Architecture Examples That Actually Work</title><link>https://kdpisda.in/10-real-world-event-driven-architecture-examples-that-actually-work/</link><pubDate>Sun, 07 Dec 2025 13:02:56 +0530</pubDate><guid>https://kdpisda.in/10-real-world-event-driven-architecture-examples-that-actually-work/</guid><description>&lt;p&gt;Your monolith was a hero. It launched your MVP, got you to product market fit, and handled everything you threw at it. But now, it&amp;rsquo;s sending you smoke signals. API response times are creeping up, a minor bug in one module takes down the entire system, and deploying a simple feature has become a week long ritual of fear and coffee. It feels like the system is warning you that the tightly coupled, synchronous world it was built for is holding back your growth.&lt;/p&gt;</description></item><item><title>Event Driven Architecture Patterns: Your Guide to Building Scalable Apps That Don't Break</title><link>https://kdpisda.in/event-driven-architecture-patterns-your-guide-to-building-scalable-apps-that-dont-break/</link><pubDate>Sat, 06 Dec 2025 13:00:59 +0530</pubDate><guid>https://kdpisda.in/event-driven-architecture-patterns-your-guide-to-building-scalable-apps-that-dont-break/</guid><description>&lt;p&gt;Let&amp;rsquo;s be honest. Event driven architecture can sound like one of those buzzwords engineers throw around to sound smart. But it&amp;rsquo;s not just jargon; it&amp;rsquo;s a totally different way of thinking about how the parts of your application talk to each other. I remember the first time I really got it, it felt like a lightbulb moment.&lt;/p&gt;
&lt;p&gt;Instead of services directly calling each other and waiting for a response (the digital equivalent of being put on hold), they just announce things that have happened. &amp;ldquo;Hey, a new user signed up!&amp;rdquo; Other services that care can listen in and react. This creates systems that are incredibly decoupled, scalable, and way more resilient to the chaos of the real world.&lt;/p&gt;</description></item></channel></rss>