<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Blog on Om Ingale</title><link>https://omingale.in/blog/</link><description>Recent content in Blog on Om Ingale</description><generator>Hugo -- 0.149.0</generator><language>en-us</language><lastBuildDate>Tue, 20 Oct 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://omingale.in/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Event Driven Architecture on AWS</title><link>https://omingale.in/blog/event-driven-architecture/</link><pubDate>Tue, 20 Oct 2026 00:00:00 -0500</pubDate><guid>https://omingale.in/blog/event-driven-architecture/</guid><description>&lt;h2 id="what-is-event-driven-architecture"&gt;What is Event-driven Architecture?&lt;/h2&gt;
&lt;p&gt;Event-driven architecture or EDA is a software design pattern where the system produces and responds to events. The fundamental concept of responding to an event or a text input is not new, and has been used from early 1970s. Lets understand what an event actually means.&lt;/p&gt;
&lt;h2 id="what-is-an-event"&gt;What is an event?&lt;/h2&gt;
&lt;p&gt;An event is a change in state, the significance of the change depends on the domain of the system, hence it can be defined as &lt;strong&gt;significant change&lt;/strong&gt; in state.
An example of event could be&lt;/p&gt;</description></item></channel></rss>