Crafting Resilient and Scalable Systems with Orchestration and Choreography Patterns on Kubernetes
summary
Shows a working event driven care plan: provider availability posts to a Kafka topic, a Spring Boot service writes bookings to PostGIS, and Argo Workflows is triggered to reserve rooms and notify patients so the demo proves the flow end to end. Compares Saga choreography vs orchestration with concrete tradeoffs, uses Apache Kafka (self‑hosted or Amazon MSK) and Argo Workflows plus Argo Events, warns about Strimzi operators, broker placement across AZs and Argo controller CR scalability limits.
AI-written summary · about
chapters (7)
- 0:00Event-driven architectures intro
- 3:54Choreography vs orchestration
- 10:09When to use orchestration
- 15:10Healthcare workflow demo
- 20:26Deploy Kafka & Argo Workflows
- 23:23Scaling Kafka & Argo Workflows
- 27:00Summary & resources
related talks
44mGetting started with Orchestration and Choreography in Distributed Applications
52mCloud-Native Kubernetes Workflows on AKS with Argo
39mBuild and Deploy Your Application with Argo on Kubernetes
52mCloud-Native Kubernetes Workflows on AKS with Argo
27mBuilding a Data Science Platform with Argo Workflows
02h 25mFrom Orchestration to Choreography, from Practice to Theory
42mOrchestration vs Choreography, A Guide To Composing Your Monolith
27mEmpowering Resilient Scalability: The Power of Choreography in Distributed Systems