Choreography vs Orchestration in serverless microservices
summary
Compares three concrete architectures and shows working demos that wire Cloud Functions, Cloud Run, external APIs and connectors into Google Cloud Workflows; claims Workflows can handle millions of steps per second and demonstrates chaining, parallel branches, waits, retries and saga/compensation pattern for failures. Shows an image pipeline triggered by Eventarc that calls filter → label → resize → watermark and writes a labeled 400×400 image, and links to runnable code on GitHub and slides on SpeakerDeck.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:06Simple REST: Pros and Cons
- 6:11Choreography: Pros and cons Pros
- 10:16Orchestration: Pros and cons
- 14:53Hybrid approach
- 19:47CNCF Serverless Workflow
- 28:02Errors and retries
- 38:08Retries and saga pattern
- 47:183 different event formats
- 48:11Lessons Learned
related talks
38mChoreography vs Orchestration in serverless microservices
32mChoreography vs Orchestration in serverless microservices
51mChoreography vs Orchestration in serverless microservices
49mChoreography vs Orchestration in serverless microservices
50mChoreography vs Orchestration in serverless microservices
46mChoreography vs Orchestration in serverless microservices
46mChoreography vs Orchestration in serverless microservices
01h 03mChoreography vs Orchestration in serverless microservices
