Resilience of Systems - Azure Availability Zones
The EUM platform is operated on a redundant infrastructure set up on Microsoft Azure operated securely in multiple geographies around the world. See Data Center Locations and Physical Security | Extranet User Manager. The availability of this system is guaranteed through the Microsoft Azure Cloud.
Azure Availability Zones are unique physical locations within an Azure region that protect your applications and data from data centre failures.
To ensure business continuity and disaster recovery (BCDR), there’s a minimum of three separate zones in all enabled regions. We build high-availability into our application architecture by co-locating your compute, storage, networking, and data resources within a zone and replicating them in other zones.
Benefits of Availability Zones
Physical isolation – When possible, Azure prefers at least 300 miles of separation between data centres in an Availability Zone, although this isn't practical or possible in all geographies. Physical data centre separation reduces the likelihood of natural disasters, civil unrest, power outages, or physical network outages affecting both regions at once. Isolation is subject to constraints within the geography (geography size, power/network infrastructure availability, regulations, etc.).
Platform-provided replication - With zone-redundant services (ZRS), replication of data is performed automatically to protect resources from single points of failure. Zone redundant storage, for example, replicates the data across three zones so that a zone failure won't impact the high availability of the data.
Scale and high availability - Increase scale, ensure rapid recovery, and maintain data integrity for all your applications. Seamlessly recover from site failure while reducing the complexity of availability using zone-redundant services. Lower the cost of site recovery with automated data replication, while enabling active-active scaling with low-latency data replication.
Data residency – An Availability Zone resides within the same geography as assigned to the Azure service.
For more information, see: