Skip to content

Commit 3d26fcf

Browse files
authored
Merge pull request #174705 from msmbaldwin/resiliancy
Updated two, added two resilience articles,
2 parents 6ce120a + acedbbb commit 3d26fcf

16 files changed

+470
-414
lines changed

articles/availability-zones/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,12 @@
1010
href: az-overview.md
1111
- name: Availability Zones Documentation
1212
items:
13+
- name: Azure Services
14+
href: region-types-service-categories-azure.md
1315
- name: Azure Services that support Availability Zones
1416
href: az-region.md
17+
- name: Terminology
18+
href: glossary.md
1519
- name: Virtual machines
1620
items:
1721
- name: Create a Linux VM in an Availability Zone with CLI

articles/availability-zones/az-overview.md

Lines changed: 42 additions & 187 deletions
Large diffs are not rendered by default.

articles/availability-zones/az-region.md

Lines changed: 195 additions & 226 deletions
Large diffs are not rendered by default.
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: Azure resiliency terminology
3+
description: Understanding terms
4+
author: prsandhu
5+
ms.service: azure
6+
ms.topic: conceptual
7+
ms.date: 10/01/2021
8+
ms.author: prsandhu
9+
ms.reviewer: cynthn
10+
ms.custom: fasttrack-edit, mvc
11+
---
12+
13+
# Terminology
14+
15+
To better understand regions and availability zones in Azure, it helps to understand key terms or concepts.
16+
17+
| Term or concept | Description |
18+
| --- | --- |
19+
| region | A set of datacenters deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network. |
20+
| geography | An area of the world that contains at least one Azure region. Geographies define a discrete market 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 our dedicated high-capacity networking infrastructure. |
21+
| availability zone | Unique physical locations within a region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. |
22+
| recommended region | A region that provides the broadest range of service capabilities and is designed to support availability zones now, or in the future. These regions are designated in the Azure portal as **Recommended**. |
23+
| alternate (other) region | A region that extends Azure's footprint within a data-residency boundary where a recommended region also exists. Alternate regions help to optimize latency and provide a second region for disaster recovery needs. They aren't designed to support availability zones, although Azure conducts regular assessment of these regions to determine if they should become recommended regions. These regions are designated in the Azure portal as **Other**. |
24+
| cross-region replication (formerly paired region) | A reliability strategy and implementation that combines high availability of availability zones with protection from region-wide incidents to meet both disaster recovery and business continuity needs. |
25+
| foundational service | A core Azure service that's available in all regions when the region is generally available. |
26+
| mainstream service | An Azure service that's available in all recommended regions within 90 days of the region general availability or demand-driven availability in alternate regions. |
27+
| strategic service | An Azure service that's demand-driven availability across regions backed by customized/specialized hardware. |
28+
| regional service | An Azure service that's deployed regionally and enables the customer to specify the region into which the service will be deployed. For a complete list, see [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=all). |
29+
| non-regional service | An Azure service for which there's no dependency on a specific Azure region. Non-regional services are deployed to two or more regions. If there's a regional failure, the instance of the service in another region continues servicing customers. For a complete list, see [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=all). |
30+
| zonal service | An Azure service that supports availability zones, and that enables a resource to be deployed to a specific, self-selected availability zone to achieve more stringent latency or performance requirements. |
31+
| zone-redundant service | An Azure service that supports availability zones, and that enables resources to be replicated or distributed across zones automatically. |
32+
| always-available service | An Azure service that supports availability zones, and that enables resources to be always available across all Azure geographies as well as resilient to zone-wide and region-wide outages. |
180 KB
Loading
102 KB
Loading
180 KB
Loading
Lines changed: 3 additions & 0 deletions
Loading
Lines changed: 6 additions & 0 deletions
Loading
Lines changed: 8 additions & 0 deletions
Loading

0 commit comments

Comments
 (0)