Choreography vs Orchestration in serverless microservices
summary
Compares three concrete patterns and shows working demos: Google Cloud Workflows orchestrates Cloud Run, Cloud Functions and external APIs (SendGrid via Secret Manager) with built-in OIDC/OAuth, retries (default 5 tries), callbacks and connectors; Eventarc + Workflows demo processes images through four functions (filter, labeler, resizer, watermarker) triggered from storage and it runs end-to-end; parallel BigQuery queries drop total time from ~60s to ~20s; samples and YAML/JSON workflow definitions are on GitHub and Speaker Deck.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:07Direct service-to-service calls
- 4:57Indirect via events (choreography)
- 8:35Imagine a more complex scenario
- 9:23A central orchestrator
- 28:52Make a conscious choice
- 30:23Event-driven orchestration
- 32:02Handle errors with retries and saga pattern
- 35:39Combine serverful workloads with serverless
related talks
50mChoreography vs Orchestration in serverless microservices
32mChoreography vs Orchestration in serverless microservices
51mChoreography vs Orchestration in serverless microservices
50mChoreography vs Orchestration in serverless microservices
49mChoreography vs Orchestration in serverless microservices
46mChoreography vs Orchestration in serverless microservices
46mChoreography vs Orchestration in serverless microservices
01h 03mChoreography vs Orchestration in serverless microservices
