This post is part of a series of posts showing how to create a “minimum viable ARM template” and how to modify it to suit various scenarios. To see the full list of posts in this series, see this page: https://negatblog.wordpress.com/minimum-viable-arm-templates/. Azure has a concept of an “availability set”: all VMs in an availability set get…… Continue reading Minimum Viable Template: Place a VM in an Availability Set
Tag: high availability
Minimum Viable Templates: Put a VM in an Availability Zone
This post is part of a series of posts showing how to create a “minimum viable ARM template” and how to modify it to suit various scenarios. To see the full list of posts in this series, see this page: https://negatblog.wordpress.com/minimum-viable-arm-templates/. Availability Zones allow us to spread our resources across different physical locations within a…… Continue reading Minimum Viable Templates: Put a VM in an Availability Zone
Scale Sets and Load Balancers
Scale sets provide scalable, highly-available compute, but compute in a vacuum is not useful in most cases. It is often necessary to have an additional component route traffic to the VMs in the scale set. Highly-available, platform-managed load balancers like the Azure Load Balancer and Azure Application Gateway can route traffic to scale set VMs…… Continue reading Scale Sets and Load Balancers
High Availability On Azure
If your app is hosted on a single virtual machine, this virtual machine is a single point of failure. This means that any single thing that goes wrong on this machine (hardware failure, networking blip, etc.) can cause your app to fail completely. To avoid this, Azure offers components that allow you to build a…… Continue reading High Availability On Azure