Finding Harmony in Distributed Systems: Choreography vs Orchestration in Software Dev
summary
Compares two concrete architectures: message passing choreography where independent services handle events (examples: parking‑garage sensors, Google Docs, ride‑sharing) offering scalability and resilience, and a central orchestrator model (BPM workflows, CI/CD pipelines, ETL, supply chain, Domino’s ordering) that enforces ordered state transitions, easier observability and consistency but introduces a single point of failure and heavier change management. Recommends choosing by requirement: predictability/state machines favor orchestration, explosive scale and loose coupling favor choreography, and hybrid patterns often work in production.
AI-written summary · about
chapters (10)
- 0:00Introduction to distributed systems
- 1:15Choreography vs orchestration overview
- 2:20Choreography explained with examples
- 5:51Pros and cons of choreography
- 8:40Applications suited for choreography
- 11:35Orchestration explained with examples
- 14:27Pros and cons of orchestration
- 15:54Applications suited for orchestration
- 18:49Choosing between the two approaches
- 22:23Final thoughts and call to action
related talks
32mBalancing Choreography & Orchestration
38mChoreography vs Orchestration in long running asynchronous processes
44mGetting started with Orchestration and Choreography in Distributed Applications
27mEmpowering Resilient Scalability: The Power of Choreography in Distributed Systems
47mComplex event flows in distributed systems
52mLoosely or lousily coupled? Understanding communication patterns
02h 25mFrom Orchestration to Choreography, from Practice to Theory
58mElements of Distributed Architectures