Course contentsShow
← System Design
Lesson 592 of 1,91916. Distributed TransactionsFree lesson

Choreography vs Orchestration Tradeoffs

Comparing decentralized choreography with centralized orchestration for complexity, coupling, and observability.

Choreography vs Orchestration Tradeoffs

What you'll learn: How to decide between decentralized choreography and centralized orchestration when implementing sagas based on complexity, coupling, and observability needs.

The Core Decision

Both choreography and orchestration solve the saga pattern's coordination problem, but in fundamentally different ways. Choosing between them means weighing three critical dimensions: system complexity, component coupling, and operational visibility.

Key Tradeoff Dimensions

Complexity and Control Flow

Choreography distributes logic across services—each listens for events and decides what to do next. There's no central "map" of the workflow. This feels simple initially (no orchestrator to build), but complexity grows as you add steps. Understanding the full transaction flow requires reading code across multiple services.

Orchestration centralizes the workflow in one orchestrator service. The entire saga lives in one place, making it easier to understand, modify, and debug. However, you now have an extra service to maintain.

Coupling

Choreography creates tight coupling through shared events. Services must know what events others emit and what they mean. Adding a new step means changing multiple services that need to react to or produce events.

Orchestration couples services to the orchestrator, but services don't need to know about each other. The orchestrator knows the workflow; participants just respond to direct commands. This makes individual services more reusable.

Observability

Choreography makes monitoring difficult. There's no single place showing saga state—you must correlate logs across services to understand what happened.

Orchestration provides natural observability. The orchestrator knows exactly where each saga stands, making monitoring, debugging, and business reporting straightforward.

Key Takeaway: Choose choreography for simple, stable workflows where autonomy matters most. Choose orchestration when workflows are complex, change frequently, or require strong monitoring—accepting the cost of an additional coordination service.