<?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 systems on Kuldeep Pisda</title><link>https://kdpisda.in/tag/event-driven-systems/</link><description>Recent content in event driven systems on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 07 Dec 2025 13:02:56 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/event-driven-systems/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>