Autoscale for App Service, available from Standard tier, that adds instances when demand rises and removes them when it falls, making it a good fit for unpredictable load.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Scale Out in context, with comparison tables and the common traps.
Terms in this definition
- Autoscale
Azure Monitor capability that adds or removes instances on a schedule or once a metric rule has been true for its full duration. The maximum instance count merely sets a ceiling and never triggers scaling itself.
- App Service
Managed PaaS hosting for web apps and Web App for Containers, run in a sandbox without OS access. Deployment slots and autoscale start at the Standard tier.
- S0 pricing tier (Foundry Tools)
Name of the standard paid tier for Foundry, Azure OpenAI and most Foundry Tools. Exceptions: Computer Vision calls its standard tier S1, and Document Intelligence offers nothing beyond F0 and S0.
- ELT
Extract, load, transform: raw data lands in the target system first and is transformed there. See ETL for the opposite order.
Related terms
- Isolated tier (App Service)
The IsolatedV2 pricing tier, in which apps are hosted on an App Service Environment deployed into a VNet you own, able to scale out as far as 100 instances.
- Runtime Scale Monitoring
Function apps on the Azure Functions Premium plan that use SQL triggers need this runtime setting turned on, so they can scale out as pending changes build up.