Scaling Azure Container Apps: Maximize Performance and Minimize Costs
summary
Azure Container Apps uses KEDA scalers (about 74 built‑in) to auto‑scale HTTP, queue and cron triggers; demos show HTTP polling defaults to 30s (demo used 10s) and a 60s cooldown, scale to zero idle pricing, and a queue demo processing 1,000 images with massive replica churn. Jobs run one image per execution with parallelism controls. Choice between consumption vs dedicated workload profiles affects cost and reserved performance; GPUs are available pay‑as‑you‑go.
AI-written summary · about
chapters (10)
- 0:00Azure Container Apps intro
- 2:55Why Azure Container Apps is great
- 10:21Azure Container Apps environment
- 19:54Scaling applications deep dive
- 23:43HTTP and queue scaling demos
- 30:12Cron and custom scaling
- 37:01Jobs in Azure Container Apps
- 43:28Jobs scaling demo
- 47:59Scaling tips and tricks
- 53:38Q&A with Azure Container Apps
related talks
01h 04mScaling Docker Containers using Kubernetes and Azure Container Service
44mBuilding and scaling cloud-native intelligent applications on Azure
46mModernizing your applications with containers and serverless
01h 07mDocker Containers on Azure - let me count the ways
20mManage Scaling, While Keeping Costs Under Control. Challenge Accepted.
20mDrive higher utilization of apps in Azure Spring Cloud with Autoscale
15mHow to scale your app in minutes with container and AWS ECS
01h 03mDeveloping microservices like a boss with Dapr and Azure Container Apps
