Orchestration vs. Choreography in Microservices
summary
Compares an actual loan‑broker workflow implemented as microservices and shows why orchestration centralizes state and commands (easy visibility but control coupling, scaling and single‑point concerns) while choreography uses events to remove temporal coupling but creates bidirectional coupling, hard compensations, versioning and observability headaches. Demonstrates an asynchronous orchestration option, mentions sagas/message brokers and tools like Kunda/Conductor, counts 34 arrows on a problematic slide, and gives a five‑question decision framework to choose per workflow.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 4:40Microservices communication shift
- 7:08Orchestration with loan broker
- 10:41Orchestration challenges
- 14:16Choreography with loan broker
- 16:45Coupling types compared
- 23:11Asynchronous orchestration
- 29:16Complex mortgage workflow
- 33:47Business failures and compensations
- 38:01Passive publishers issue
- 43:18Choreography prerequisites
- 45:43Versioning challenges
- 47:49Lack of system overview
- 50:37Coordination decision framework
- 1:00:31Recap and recommendations
related talks
59mOrchestration vs. Choreography: The good, the bad, and the trade-offs
01h 01mOrchestration vs. Choreography: The good, the bad, and the trade-offs
33mOrchestrate Your Choreography
50mChoreography vs Orchestration in Serverless Microservices
42mOrchestration vs Choreography, A Guide To Composing Your Monolith
38mChoreography vs Orchestration in long running asynchronous processes
46mChoreography vs Orchestration in serverless microservices
32mBalancing Choreography & Orchestration