Understanding Azure architecture gives you power to learn lots of higher level concepts on Azure like Virtual Machine scale sets etc. Therefore, in this article you will learn what is Azure overall architecture and its individual components like region, zones, data-centers etc.
- Geography consists of many regions
- Each Region must have minimum 3 Availability Zones.
- Each Availability Zone can have one or more Data Centers equipped with independent power, cooling, and networking.
- No two zones can share a data center.
- Each Data-Center has Availability Sets
- Each Availability Set can have 3 Fault Domains & up to 20 Update Domain
- Fault Domain is grouping of virtual machines, independent network switch and power supply provides hardware fault tolerance.
- Update Domain is logical grouping of virtual machine and included hardware that can be updated and rebooted at one time.
Azure Geography contains most of the countries in the world.
An Azure geography is a discrete market, typically containing at least one or more regions, that preserves data residency and compliance boundaries. Geographies allow customers with specific data-residency and compliance needs to keep their data and applications close. Geographies are fault-tolerant to withstand complete region failure through their connection to the dedicated high-capacity networking infrastructure of Azure.
Each Geography has multiple Regions. Example The United States has regions like Center US, East US, East US2, East US3, North Central US, South Central US, West Central US, West US, West US 2, West US 3.
An Azure region is a set of datacenters, deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network.
Azure Availability Zones are physically and logically separated datacenters with their own independent power source, network, and cooling. Connected with an extremely low-latency network, they become a building block to delivering high availability applications. Availability Zones ensure that if there’s an event impacting a datacenter site—for example, if someone cuts the power, or there are issues with cooling—your data will be protected.
Running a VM with one or more replicated copies on different Availability Zones , providing resiliency against data center failure.
Azure Availability Zones are unique physical locations within an Azure region and offer high availability to protect your applications and data from datacenter failures. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. The physical separation of availability zones within a region protects apps and data from facility-level issues. Zone-redundant services replicate your apps and data across Azure Availability Zones to protect from single points of failure.
The Azure global network refers to all of the components in networking and is comprised of the Microsoft global wide-area network (WAN), points of presence (PoPs), fiber, and others.
In the Data Center the servers are divided into multiple physical and logical groups.
An availability set is a logical grouping of VMs that allows Azure to understand how your application is built to provide for redundancy and availability.
The physical grouping of servers (virtual machines) is called Fault Domain. It is Each server share a common power source and network switch within a Fault Domain. A fault domain is a set of hardware components that share a single point of failure.
An update domain is a logical group of underlying hardware that can undergo maintenance or be rebooted at the same time. As you create VMs within an availability set, the Azure platform automatically distributes your VMs across these update domains.
Azure Availability Zone give maximum industry best 99.99% of availability.
|Manage VMs manually
|Use VM Scale Set
|Adding extra VM
|Manually create, configure and ensure compliance
|Automatically create from central configuration
|Traffic Balancing & distribution
|Automatically create and integrate Azure load balancer or Application Gateway
|High availability and redundancy
|Manually create Availability set or distribute and track VMs across Availability Zones
|Automatic distribution of VM instances across Availability Zones or Availability Sets
|Scaling of VMs
|Manual monitoring and Azure Automation
|Auto scale based on host metrics, in-guest metrics, Application Insights, or schedule
Thanks for reading my article till end. I hope you learned something special today. If you enjoyed this article then please share to your friends and if you have suggestions or thoughts to share with me then please write in the comment box.
- Please subscribe to All-Access Membership PRO plan to access current and future angular, node.js and related courses.
- Please subscribe to All-Access Membership ELITE plan to get everything from PRO plan. Additionally, you will get access to a monthly live Q&A video call with
Rupeshand you can ask doubts/questions and get more help, tips and tricks.
Your bright future is awaiting for you so visit today FullstackMaster and allow me to help you to board on your dream software company as a new Software Developer, Architect or Lead Engineer role.