I'm just gonna define the EDA in a short talk and definitely, it's not completed. Based on the definition of Wikipedia "Event-driven architecture, is a software architecture pattern promoting the production, detection, consumption of, and reaction to events. An event can be defined as "a significant change in state". For example, when a consumer purchases a car, the car's state changes from "for sale" to "sold"."
In another definition, EDA is a framework that orchestrates the behavior around the production and consumption of events which consists of event creators and event consumers. The creator only knows that the event has occurred and the consumers need to know about the creators that if they have happened or not. And that's the main benefit of event-driven architecture which enables large numbers of creators and consumers to exchange status, messages, and responses.
When your system is in real time processing or several parts of the applications are processing on an event, you can apply EDA. One of the benefits of EDA is that producer and consumer are decoupled and Consumers can respond to events immediately.
Category: Software