Choreography vs Orchestration in serverless microservices
summary
Compares event-driven choreography with centralized orchestration using concrete Google tooling: Google Workflows calling Cloud Functions, Cloud Run and external APIs, triggered by EventArc, defined in YAML and visualized in the console. Claims orchestration captures the business flow, surfaces which step failed, centralizes retries and supports the saga pattern for compensations, parallel branches, and executions up to one year. Shows demos and a GitHub repo. Notes tradeoffs: lost event flexibility, another service to operate, potential single point of failure, and harder local unit testing.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:41EventDriven Choreography
- 4:54EventDriven Pros and Cons
- 8:52Orchestration Pros and Cons
- 11:49Which one is better
- 14:00Orchestration landscape
- 16:33Orchestration service workflows
- 24:15Orchestration UI
- 24:29Orchestration with Choreography
- 35:50Parallelization
- 38:28Case study
related talks
32mChoreography vs Orchestration in serverless microservices
49mChoreography vs Orchestration in serverless microservices
46mChoreography vs Orchestration in serverless microservices
51mChoreography vs Orchestration in serverless microservices
01h 03mChoreography vs Orchestration in serverless microservices
50mChoreography vs Orchestration in Serverless Microservices
38mChoreography vs Orchestration in serverless microservices
50mChoreography vs Orchestration in serverless microservices
