GLOSSARY

A design approach in which components produce, detect, and respond to events representing changes or occurrences in a system.

EDA can reduce coupling, improve responsiveness, and let multiple processes react to the same business event. It supports scalable integration and near-real-time automation.

When an order is confirmed, an event triggers inventory reservation, customer notification, analytics, and fulfilment independently rather than through one synchronous chain.

Asynchronous systems are harder to trace, test, and reason about. Duplicate, delayed, or out-of-order events are normal design concerns, and eventual consistency may not suit every process.

Producers publish events without directly controlling consumers. Brokers, streams, or queues distribute them to interested services, which react asynchronously. Designs must address event contracts, delivery guarantees, ordering, idempotency, schema evolution, retries, and observability.