Getting started with Orchestration and Choreography in Distributed Applications
summary
Clear rule: use orchestration for strict intra‑domain sequencing and retries and choreography to decouple services with events. Practical stack: Step Functions + EventBridge with Lambda, DynamoDB, S3, Rekognition, Transcribe/Polly and websockets. Implements per‑order state machines, Saga compensations for failures, and idempotency to avoid double charges. Production proof: a Serverless Espresso demo runs on free tier (~1,000 coffees/day) and has 50,000 coffees served across events, showing the pattern scales and the workflow UI and auditing actually work.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 1:54Problem of task coordination
- 5:44Orchestration with state machines
- 9:58AWS Step Functions demo
- 11:23Decoupling microservices
- 13:31Event choreography basics
- 17:19Event bus patterns in AWS
- 22:13Event design best practices
- 26:51Error handling with Saga pattern
- 28:55When to use orchestration vs choreography
- 30:43Real-world serverless coffee shop demo
- 37:05Key takeaways and resources
related talks
41mGetting started with Orchestration and Choreography in Distributed Applications
32mChoreography vs Orchestration in serverless microservices
46mChoreography vs Orchestration in serverless microservices
49mChoreography vs Orchestration in serverless microservices
51mChoreography vs Orchestration in serverless microservices
37mBuild next-gen applications with event-driven architectures
42mOrchestration vs Choreography, A Guide To Composing Your Monolith
38mChoreography vs Orchestration in long running asynchronous processes