changedatacapture.net • Read the Article

EDA Patterns Part 2

Orchestration vs choreography, pattern analysis, and a practical decision framework.

EDA Orchestration and Patterns

The second part of the event-driven architecture series. Covers orchestration vs choreography in microservices, good patterns such as the outbox and idempotency, anti-patterns to avoid, and a decision guide for choosing between events, commands, and workflows.

What this series covers

Part 1 : When Not to Use EDA

Why event-driven design is useful, when it becomes overkill, and the temporal difference between events, commands, and queries.

Read Part 1
Part 2 : Patterns and Decisions

Orchestration vs choreography, five good patterns, five anti-patterns, and a practical decision table for choosing the right approach.

Read Part 2

Interactive Tool

Use the EDA Decision Matrix to analyze your specific flow and get a pattern recommendation based on temporal intent, downstream topology, and compensation requirements.

Open EDA Decision Matrix

Quick Reference: Decision Table

If the flow is... Consider...
Asking for information now Synchronous API or read model
Asking something to happen Command or API
Telling others something happened Event
A simple chain of independent reactions Choreography
A complex business process Orchestration

Related tools

EDA Decision Matrix
Part of: Event-Driven Architecture