Event-driven Architecture is the best fit design pattern… or not
In which cases is-it relevant ?
An event-driven architecture is a design pattern in which the flow of control within a system is determined by events that are triggered by external or internal factors. In this type of architecture, events are handled asynchronously, which means that they do not block the main execution flow of the system. Instead, they are passed to a separate event handling mechanism, which processes the event and takes any necessary action.
What’s an Event ?
An event is typically defined as a change in state or a trigger that occurs within a system or application. It can be triggered by external factors, such as user input or data being received from another system, or it can be triggered by internal processes or conditions.
An event can be thought of as a message or notification that is generated by a system or component and passed to another system or component for handling. This process is often referred to as «event-driven» or «event-driven architecture.»
