How we achieved extreme scale under the hood in Azure Functions
summary
Deep dive into Azure Functions Flex Consumption: rewritten architecture (Legion + placeholder pools) that uses App Insights, Azure Load Test (JMeter engine) and Cosmos DB to hit extreme throughput, e.g. burst to 1000 instances in under a minute and customer tests reaching 1.6 million requests per second. Workloads run in containers on nested VMs, concurrency is a tunable knob (defaults: 2GB → 16 concurrency; Python = 1), placeholder specialization reduces cold starts, and experiments show higher concurrency cuts instance count and cost.
AI-written summary · about
chapters (8)
- 0:00Extreme scale in Azure Functions
- 5:27Testing at scale goals
- 14:38High-throughput telemetry demo
- 26:39Architecture deep dive
- 39:46Concurrency in Flex Consumption
- 55:35Concurrency settings metrics
- 1:00:03Placeholder pools cold start
- 1:01:48Max scale tips
related talks
59mAzure Serverless for JavaScript TypeScript Folks
52mHands-on Workshop: Refactor Node.js and Express APIs to Serverless APIs with Azure Functions
18mScaling Kubernetes-Native Systems with Event-Driven Patterns on Azure
56mServerless microservices with Azure Container Apps
44mAzure and Containers, the tale of the two inseparable friends
44mHop on the Serverless Adventure with NodeJS
28mHop on the serverless adventure with NodeJS
31mLessons from Scaling GraphQL to Half a Billion Requests per Minute
