<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>resilient systems on Kuldeep Pisda</title><link>https://kdpisda.in/tag/resilient-systems/</link><description>Recent content in resilient systems on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 06 Dec 2025 13:00:59 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/resilient-systems/index.xml" rel="self" type="application/rss+xml"/><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><item><title>High Availability Architecture That Actually Works</title><link>https://kdpisda.in/high-availability-architecture-that-actually-works/</link><pubDate>Wed, 26 Nov 2025 12:26:15 +0530</pubDate><guid>https://kdpisda.in/high-availability-architecture-that-actually-works/</guid><description>&lt;p&gt;It always starts with that frantic 3 AM alert: &lt;em&gt;&amp;lsquo;The site is down.&amp;rsquo;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We have all been there. That sinking feeling as you scramble to figure out what just broke is a rite of passage for many of us in the industry. I still remember the cold sweat from my first major production outage; it felt like the entire internet was staring at me.&lt;/p&gt;
&lt;p&gt;This guide is for every engineer who has stared at that error screen and vowed, &amp;ldquo;never again.&amp;rdquo; We are not talking about abstract theory here; we are talking about practical, battle tested high availability architecture that keeps your services running, your users happy, and most importantly, lets you get a good night&amp;rsquo;s sleep.&lt;/p&gt;</description></item></channel></rss>