<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>event driven architecture patterns on Kuldeep Pisda</title><link>https://kdpisda.in/tag/event-driven-architecture-patterns/</link><description>Recent content in event driven architecture patterns 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/event-driven-architecture-patterns/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></channel></rss>