Software Architecture Foundations · Architecture Styles Used Today
Event-Driven Architecture
Design systems around events, asynchronous workflows, and eventual consistency.
Event-Driven Architecture
Event-driven architecture (EDA) models important business changes as events. Instead of one service calling every downstream system synchronously, a producer publishes an event such as OrderPlaced, PaymentCaptured, or UserRegistered, and interested consumers react independently.
When It Fits
EDA fits workflows that can be asynchronous, need loose coupling, or must fan out to many consumers. It is common in ecommerce, notifications, analytics, billing, audit trails, and integration between bounded contexts.
Design Rules
- Use events for facts that already happened, not commands disguised as facts.
- Make consumers idempotent because messages may be retried.
- Use durable brokers, dead-letter queues, replay strategy, and schema versioning.
- Choose ordering guarantees deliberately; global ordering is expensive and rarely needed.
Tradeoffs
| Benefit | Cost |
|---|---|
| Loose coupling and scalable fan-out | Harder tracing and debugging |
| Better resilience to downstream outages | Eventual consistency and duplicate handling |
| Replayable history when retained | Schema governance and retention cost |
Practice questions
How would you explain event-driven architecture in a production design review?
Answer
Summary
I would explain event-driven architecture as a design choice driven by requirements, constraints, and failure modes.
Longer Answer
I would explain event-driven architecture as a design choice driven by requirements, constraints, and failure modes. The main decision is whether the workflow can tolerate asynchronous, eventually consistent processing.
Key Points
- I would explain event-driven architecture as a design choice driven by requirements, constraints, and failure modes
- The main decision is whether the workflow can tolerate asynchronous, eventually consistent processing
- Good architecture answers connect event-driven architecture to scalability, reliability, security, cost, and team operations
- Use the answer to connect the concept back to a realistic production or interview scenario for 'How would you explain event-driven architecture in a production design review?'
Comparison / Tradeoffs
| Aspect | Notes |
|---|---|
| Core idea | I would explain event-driven architecture as a design choice driven by requirements, constraints, and failure modes. |
| Practical tradeoff | Good architecture answers connect event-driven architecture to scalability, reliability, security, cost, and team operations. |
Why
Summary
Good architecture answers connect event-driven architecture to scalability, reliability, security, cost, and team operations.
Longer Answer
Good architecture answers connect event-driven architecture to scalability, reliability, security, cost, and team operations. In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview.
Key Points
- Good architecture answers connect event-driven architecture to scalability, reliability, security, cost, and team operations
- In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview
- In an interview, relate 'How would you explain event-driven architecture in a production design review?' to implementation decisions, tradeoffs, and operational impact
- Use the answer to connect the concept back to a realistic production or interview scenario for 'How would you explain event-driven architecture in a production design review?'
Comparison / Tradeoffs
| Aspect | Notes |
|---|---|
| Core idea | Good architecture answers connect event-driven architecture to scalability, reliability, security, cost, and team operations. |
| Practical tradeoff | In an interview, relate 'How would you explain event-driven architecture in a production design review?' to implementation decisions, tradeoffs, and operational impact. |
Open in the app to mark lessons complete, take notes and track your progress.