As we've covered availability sets Microsoft has also begun to introduce Availability Zones throughout
their regions.
Now they're not available in every region.
So it is important to look at the regions when you are planning for Availability Zones and make sure
they are available.
But essentially they work similar to availability sets.
But now we get ninety nine point nine nine percent availability.
They minimize the impact of planned and unplanned downtime and really just enforce them like availability
sets.
But now you choose your specific zone in Azure.
So in availability sets you know we had those fault domains and update domains.
What we do with Availability Zones is we essentially just choose the zone in fact when you building
your virtual machine you'll get a number of Availability Zones are available in a region you'll get
to choose those instead of availability set.
So it's all a either or option you can have availability sets now in the regions that have zones they
want to move you towards zones but essentially you choose the zone number.
So if you're building a VM one VM will go in availability zone zero one will go into repeatability zone
one and then you know that they're in separate data centers in the same region.
Now the latency is such that it's such a fast connection between the two data centers in the region
itself so there's no performance impact by using zones but they do get much better redundancy in fact
there was a region outage in South Central at one point where the data center essentially had some power
issues and went down and you know just because you're in an availability set did not help you.
You were completely out or the backup generators and things didn't kick in properly and people had complete
outages but Availability Zones would be two data centers.
You know further enough apart to make sure that in the event of something like that happening you would
still be online providing your machine was in the other availability zone.
So no these in addition to availability sets.