Orchestration vs. Choreography: The good, the bad, and the trade-offs
summary
Compares two coordination styles using a loan-broker banking workflow: customer request → payment → credit scoring → eligible banks → quotes → ranking; shows orchestrator storing centralized state, sending commands, and struggling with contention and coupling, while choreography uses an event bus (message broker) but creates scattered state, hard-to-handle compensating flows (notary refunds, undo provisions) and versioning pain. Offers a practical decision tool — a five-question framework (sync vs async, coupling direction, compensations, change probability, ownership) and stresses observability and small-scope workflows.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 3:36Microservices trade-offs
- 5:46Orchestration vs choreography
- 7:33Loan broker orchestration
- 11:21Loan broker choreography
- 13:47Coupling in distributed systems
- 18:43Synchronous vs async orchestration
- 26:10Choreography downsides
- 33:55Service boundaries
- 37:06Regulation changes
- 41:02Versioning challenges
- 42:49Observability needs
- 45:16Coordination patterns
- 51:19Five questions
- 54:30Service boundaries validation
- 58:00Embracing change
- 59:46Trade-offs
related talks
59mOrchestration vs. Choreography: The good, the bad, and the trade-offs
01h 13mOrchestration vs. Choreography in Microservices
33mOrchestrate Your Choreography
42mOrchestration vs Choreography, A Guide To Composing Your Monolith
32mBalancing Choreography & Orchestration
38mChoreography vs Orchestration in long running asynchronous processes
50mChoreography vs Orchestration in Serverless Microservices
46mChoreography vs Orchestration in serverless microservices