Glossary · E
Event-driven architecture
Systems that react to published events
What it means
In event-driven architecture, components publish information about events and other components react to it. An event describes something that happened, such as an order being placed. This can reduce direct coupling, but delivery guarantees, ordering and duplicate handling still need careful design.
What it means for a business
An order event can trigger stock reservation, customer communication and reporting updates in different services. Each consumer needs rules for retries and duplicate events so that a repeated message does not create repeated business actions.