What is Event-Driven Architecture?
Event-driven architecture (EDA) is a design pattern where system components communicate by producing and consuming events — asynchronous notifications that something happened.
Event-driven architecture (EDA) is a design pattern where system components communicate by producing and consuming events — asynchronous notifications that something happened. Instead of direct request-response calls, services emit events that other services react to.
Patterns: Event notification (simple notification that something happened), Event-carried state transfer (event contains the data, not just a reference), Event sourcing (store all events as the source of truth, derive current state from event history), and CQRS (separate read and write models, connected by events).
Tools: Apache Kafka (distributed event streaming), RabbitMQ (message broker), AWS SNS/SQS (managed messaging), and NATS (lightweight messaging). EDA enables loose coupling, scalability, and resilience — but adds complexity in debugging and maintaining event ordering.
Why It Matters
Event-driven architecture enables loose coupling between services, natural scalability (add consumers without changing producers), and temporal decoupling (producer and consumer don't need to be available at the same time).
Frequently Asked Questions
What is event-driven architecture?
A design pattern where components communicate via asynchronous events rather than direct calls. Services produce events (something happened) and other services consume and react to them.
When should I use EDA?
When services need loose coupling, when operations can be asynchronous, when you need audit trails, or when multiple services need to react to the same event. Don't use for simple synchronous request-response flows.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →