From Orchestration to Choreography and Back
summary
A ten-year case study of a high-throughput data processing pipeline handling 500 million messages per day, describing its architectural evolution from choreography-based design to fully centralized orchestration and back. The talk explains the specific shift between choreography and orchestration approaches and the practical lessons learned during that evolution.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:57Pipeline plans
- 8:16Pipeline tools
- 11:35Service disintegration
- 12:59Messaging patterns
- 15:31Microservice problems
- 21:10Simple architecture
- 23:18Choreography vs orchestration
- 27:58Selective consumer
- 30:03Results and benefits
- 31:11Conclusion
- 32:38Q&A
related talks
38mChoreography vs Orchestration in long running asynchronous processes
42mOrchestration vs Choreography, A Guide To Composing Your Monolith
02h 25mFrom Orchestration to Choreography, from Practice to Theory
33mOrchestrate Your Choreography
59mOrchestration vs. Choreography: The good, the bad, and the trade-offs
32mBalancing Choreography & Orchestration
44mGetting started with Orchestration and Choreography in Distributed Applications
46mChoreography Architecture, a Communication Style on nodejs