Microservices Orchestration with
summary
Clear recommendation: don't do microservices initially — start as a modular monolith, extract domains only when scaling, tech diversity, or maintainability demand it. Concrete stack: Azure Container Apps + Kada + Deer + Docker + AKS background with container registries and CI/CD. Demo builds a 3x3 whack-a-mole game with four services (proxy, realtime, game, score), 30s rounds, 50-mole scoring threshold; system autoscaled score services to six replicas and handled live traffic successfully. Specifics on revisions, ingress options, and environment partitioning come with code and GitHub Actions.
AI-written summary · about
chapters (20)
- 0:00Microservices in Azure Container Apps
- 1:03Avoid microservices for new systems
- 3:29When microservices make sense
- 5:59Monolith to microservices step-by-step
- 7:01Azure Container Apps vs others
- 9:30Container Apps structure
- 11:59Ingress configuration
- 14:07Kubernetes vs Container Apps
- 15:09Tools: Docker, Keda, Dapr
- 16:35Containers vs code deployment
- 18:39Messaging and Keda autoscaling
- 19:42Dapr for resilient communication
- 21:50Dapr local vs cloud config
- 22:30Demo: Whack-a-Mole game
- 24:37Azure setup for microservices
- 25:19Live demo: Scaling apps
- 26:24Playing Whack-a-Mole
- 29:17Scaling behavior analysis
- 30:22Cost optimization with zero scaling
- 30:42Closing remarks
related talks
42mMicroservices are the answer - but what is the question?
37mKnee Deep in Microservices
57mUnderstanding Microservices: a guide for the monolithic developer
18mMicroservices Out In the Wild
52mI Have a Microservices Architecture and I Didn't Know.
56mModular Monolith and the Prisoner of Microdisservices
01h 14mUnderstanding Microservices: A Guide For the Monolithic Developer
45mContinuously delivering containerized, highly available microservices