Empowering Resilient Scalability: The Power of Choreography in Distributed Systems
summary
Druva migrates stateful monoliths into choreographed services using a Go framework that wires services via SNS + SQS pub/sub, an event store for producers and receivers, and per-service dedicated queues plus a worker pool for pull processing. Example: a customer creation workflow publishes a license-created event that storage, alert, provisioning and reporting consume in parallel; built-in retry/republish, dead-letter handling and an optional central controller for cross-service rollback enable visibility and recovery.
AI-written summary · about
chapters (9)
- 0:00Introduction to choreography
- 2:22Problem statement and challenges
- 5:13Orchestration approach explained
- 6:21Choreography approach explained
- 10:15Use case walkthrough
- 12:53Dhruva framework overview
- 17:48Choosing orchestration vs choreography
- 18:11Team collaboration in choreography
- 20:00Q&A session begins
related talks
44mGetting started with Orchestration and Choreography in Distributed Applications
25mFinding Harmony in Distributed Systems: Choreography vs Orchestration in Software Dev
38mChoreography vs Orchestration in long running asynchronous processes
01h 02mAsynchronous Distributed Systems
27mCrafting Resilient and Scalable Systems with Orchestration and Choreography Patterns on Kubernetes
42mOrchestration vs Choreography, A Guide To Composing Your Monolith
41mGetting started with Orchestration and Choreography in Distributed Applications
49mChoreography vs Orchestration in serverless microservices