Trade-offs: Coupling and Visibility
You'll learn: How orchestration and choreography differ in their coupling characteristics, visibility into workflows, and failure handling approaches.
The Core Trade-off
When choosing between orchestration (centralized control, lesson 1373) and choreography (decentralized collaboration, lesson 1374) for sagas and event-driven workflows, you face a fundamental tension: tight coupling with clear visibility vs. loose coupling with distributed complexity.
Orchestration: Coupled but Visible
With orchestration, a central coordinator knows the entire workflow. This creates:
- Higher coupling: Services depend on the orchestrator; it knows about all participants
- Better visibility: The coordinator tracks progress, making debugging and monitoring straightforward
- Clear failure points: When something breaks, the orchestrator knows immediately and can compensate
Think of it like a conductor leading an orchestra—everyone depends on the conductor's signals, but the conductor sees exactly who's playing and who missed their cue.
Choreography: Loosely Coupled but Opaque
With choreography, services react to events independently:
- Lower coupling: Services only know about events they care about, not other services
- Limited visibility: No single place shows the complete workflow state
- Distributed failures: Failures are harder to detect because no central observer exists
It's like dancers in a flash mob—each person knows their own moves triggered by what they see, but no one has the full picture of how the performance is going.
Which to Choose?
Use orchestration when you need strong consistency, clear audit trails, or frequently changing workflows. Accept the coupling cost for operational clarity.
Use choreography when services truly need independence, you have mature observability tooling, and workflows change infrequently.
Key Takeaway: Orchestration trades tighter coupling for workflow visibility and control; choreography achieves loose coupling at the cost of distributed state and harder debugging—choose based on your team's operational maturity and business requirements.