Diagram
A system architecture showing external traffic entering a Container Apps environment through an ingress controller, which splits requests between two active revisions using traffic weights, each revision backed by load-balanced replicas.
Implement Scaling Rules and Revision Management
Revision management is how Azure Container Apps handles application updates. Every time you deploy a change, it creates a new, immutable revision. This allows for zero-downtime deployments and easy rollbacks to a previous version if something goes wrong. You can run multiple revisions simultaneously and use traffic splitting to gradually shift user traffic from an old version to a new one, enabling strategies like blue/green deployments.
Scaling is driven by KEDA, which stands for Kubernetes Event-driven Autoscaling. KEDA allows the app to scale based on various triggers. Common triggers include HTTP concurrency (the number of simultaneous web requests), CPU utilization, or events from services like Azure Service Bus. You define scaling rules that specify the minimum and maximum number of replicas. Setting the minimum to zero allows the app to scale down completely when idle, which optimizes cost.
Domain 4 of 4
36 practice questions
Practice this DomainLast updated