Ensuring Scalability and Security for Serverless Functions on Azure
summary
Flex Consumption is a Linux-only serverless plan built on the Container Apps platform that scales to zero, supports virtual networking and bursts quickly (demo shows ~3,300 req/s under load). Concurrency defaults map to instance size (2 GB → 16, 4 GB → 32; 512 MB → 4) and max-instances currently limits at 40; a Service Bus demo forces 50 instances with concurrency=1 and 30s processing. Platform adds per-function scaling, recommends user-assigned identity and private endpoints for secure VNet integration; GitHub case hits ~1.66M events/sec across ~1,000 instances.
AI-written summary · about
chapters (15)
- 0:00Azure Functions scalability intro
- 1:25Hosting plans explained
- 9:16Core scaling characteristics
- 15:40Vertical and horizontal scaling
- 18:59Concurrency control
- 26:03Scaling HTTP triggers
- 29:14HTTP trigger scalability demo
- 34:07Scaling non-HTTP triggers
- 44:26Event Hubs scaling deep dive
- 47:43Flex Consumption per-function scaling
- 49:11Identity-based security
- 58:52Service Bus with managed identity demo
- 1:04:35Networking security
- 1:06:24VNET integration demo
- 1:09:20Case studies and Q&A
related talks
53mFlex Consumption: Build Serverless Apps with High-Throughput and Virtual Networking Features
54mUnderstanding the Serverless platform in Microsoft Azure
17mAutomatic compute scaling with serverless for Hyperscale in Azure SQL Databases
01h 01mServerless Architecture With Azure
48mBuilding applications at hyper scale with the latest Azure innovations
44mAzure Serverless: Expert Panel
21mBeyond the Basics: Production Serverless Patterns for Extreme Scale
17mCloud Computing Made Better: An AWS View on Serverless Computing