Event-Driven Architecture
Event-driven architecture centers on events: producers publish events and consumers respond to them, decoupling component communication.
Purpose
Build loosely coupled, scalable systems, well suited to asynchronous and real-time processing.
Mechanism
Components communicate through an event bus/message queue rather than direct calls. Events are immutable and one-way. Consumers subscribe to the event types they care about. Suited to microservices, real-time systems, and IoT. Event sourcing uses events as the source of state.
Use cases
- System architecture
- Asynchronous processing
- Microservices