When cloud resources are unused, they can continue to put a strain on can ISV’s budget. In contrast to legacy on-premises architectures, there is no need to over-provision compute resources for times of heavy usage.
Autoscaling on Azure can help ISVs achieve cost saving on workloads by automatically scaling up and down the resources in use to better align capacity to demand. This practice can reduce spend for those dynamic workloads with inherently “peaky” demand.
For periods when your application has more demand on cloud resources, autoscaling adds resources to handle the load while accounting for performance and availability. And for those times when the load demand decreases, autoscaling can remove resources to reduce costs. It automatically scales between the minimum and maximum number of instances and will run, add, or remove VMs automatically based on a set of rules.
Not only does it increase capacity only when required, ISVs can also reduce the need for an operator to monitor performance and make decisions about resources.
Azure provides built-in autoscaling using Azure Monitor autoscale for most compute options, including:
Azure Monitor autoscale provides a common set of autoscaling functionality for virtual machine scale sets, Azure App Service, and Azure Cloud Service. Scaling can be performed on a schedule, or based on a runtime metric, such as CPU or memory usage.