Let's talk about how azure provides redundancy within a region.
If you look closely at the map, you'll see that some regions have a diamond inside, and the legend says that those regions have availability zones.
Some examples are West US two. Central, US and East US.
what our availability zones
Availability zones are physical separate data centers within an azure region.
Unlike region pairs that are required to be at least 300 miles apart, availability zones are in a closer proximity and are connected through a private, high speed fiber optic network.
Each availability zone consists of one or more data centers equipped with independent power cooling and networking.
Similarly to the region, pairs if one's own, goes down, the other continues. Working
availability zones are important for core infrastructure services like virtual machines, managed disks. I P addresses load balancers, or SQL databases.
You can architect your application for higher availability by colic, aiding your compute storage, networking and data resources within a single availability zone and duplicating the same resources into another zone.
But be aware that there could be a cost tied to duplicating your resources in multiple zones.
There are two categories of resources that support availability zones.
Some zonal resources are VMS like managed disks or I P addresses, where you specify the availability zone at the resource creation.
And there are also other zone redundant services, like storage and SQL databases, where the platform automatically replicates across zones.
Everything we've discussed so far in this module allows us to build highly available and performant applications.
This brings us to service level agreements, which we will discuss in the next video.