Azure VM Contd
- Choosing a Region for deploying Azure Infrastructure
- From the location where your customers will be using the application try to run tests by navigating Refer Here
- Consider the following datacenter (non Azure) and try to come up with different failure scenarios for website.
- Failure Scenarios:
- Each rack has parallel power supply and network. If due to some technical issue if power/network for that rack is down, The vm cannot be accessed.
- Solution: Rather than running one VM create redundancy and ensure the vms are created in different racks
- Solution: Rather than running one VM create redundancy and ensure the vms are created in different racks
- Since we are running our application on VM which runs on some physical server, there might be some maintenance (OS Updates/ Security updates) which requires restart that might lead to down times
- Do the updates/restarts in such a way that atleast one vm is running for web and one vm for database.
- The whole datacenter is down due to some natural disaster etc
- Running the solution in different datacenters in different locations can be the solution
- Running the solution in different datacenters in different locations can be the solution
- The application which is deployed on the vm (website) has faulty code:
- Solution: Developers have to fix this issue, as a workaround we need to go back to the working version. So while deploying applications also we will be ensuring atleast one vm with working version is running.
- Each rack has parallel power supply and network. If due to some technical issue if power/network for that rack is down, The vm cannot be accessed.
Azure Region Infrastructure
- Azure Regions
- There are two categories of Regions
- Region:
- Region with Zones: Refer Here
- To ensure our application running in VM is highly available, Azure has availability options
- Availability Set
- Availability Zone
- For multi-region deployments we need to understand to concept of Azure Paired Regions.
