You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/reliability/reliability-event-grid.md
+18-6Lines changed: 18 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Reliability in Azure Event Grid and Event Grid namespacess
3
-
description: Find out about reliability in Azure Event Grid and Event Grid namespaces
2
+
title: Reliability in Azure Event Grid and Event Grid namespace
3
+
description: Find out about reliability in Azure Event Grid and Event Grid namespace
4
4
author: anaharris-ms
5
5
ms.author: anaharris
6
6
ms.topic: reliability-article
@@ -9,9 +9,9 @@ ms.service: virtual-machines
9
9
ms.date: 07/02/2024
10
10
---
11
11
12
-
# Reliability in Azure Event Grid and Event Grid namespaces
12
+
# Reliability in Azure Event Grid and Event Grid namespace
13
13
14
-
This article contains detailed information on Event Grid and Event Grid namespaces regional resiliency with [availability zones](#availability-zone-support) and [cross-region disaster recovery and business continuity](#cross-region-disaster-recovery-and-business-continuity).
14
+
This article contains detailed information on Event Grid and Event Grid namespace regional resiliency with [availability zones](#availability-zone-support) and [cross-region disaster recovery and business continuity](#cross-region-disaster-recovery-and-business-continuity).
15
15
16
16
17
17
For an architectural overview of reliability in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
@@ -24,12 +24,12 @@ For an architectural overview of reliability in Azure, see [Azure reliability](/
24
24
25
25
Event Grid resource definitions for topics, system topics, domains, and event subscriptions and event data are automatically replicated across three availability zones. When there's a regional failure in one of the availability zones, Event Grid resources **automatically failover** to another availability zone without human intervention. Currently, it isn't possible for you to control (enable or disable) this feature. When an existing region starts supporting availability zones, existing Event Grid resources are automatically failed over to take advantage of this feature. No customer action is required.
26
26
27
-
**Azure Event Grid namespaces** also achieve intra-region high availability using availability zones.
27
+
**Azure Event Grid namespace** also achieves intra-region high availability using availability zones.
28
28
29
29
30
30
### Prerequisites
31
31
32
-
For availability zone support, your Event Grid resources must be in a region that supports availability zones. To review which regions support availability zones, see the [list of supported regions].(availability-zones-service-support.md#azure-regions-with-availability-zone-support).
32
+
For availability zone support, your Event Grid resources must be in a region that supports availability zones. To review which regions support availability zones, see the [list of supported regions](availability-zones-service-support.md#azure-regions-with-availability-zone-support).
33
33
34
34
35
35
### Pricing
@@ -71,6 +71,18 @@ The following table illustrates the client-side failover and geo disaster recove
71
71
| Namespaces | Supported | Not supported |
72
72
73
73
74
+
### Event grid namespace
75
+
76
+
Event Grid namespace doesn't support cross-region DR. However, you can achieve cross region high availability through client-side failover implementation by creating primary and secondary namespaces.
77
+
78
+
With a client-side failover implementation, you can:
79
+
80
+
- Implement a** custom (manual or automated) process to replicate namespace, client identities, and other configurations** including CA certificates, client groups, topic spaces, permission bindings, routing, between primary and secondary regions.
81
+
82
+
- Implement a **concierge service** that provides clients with primary and secondary endpoints by performing a health check on endpoints. The concierge service can be a web application that is replicated and kept reachable using DNS-redirection techniques, for example, using Azure Traffic Manager.
83
+
84
+
-**Achieve an Active-Active DR solution** by replicating the metadata and balancing load across the namespaces. An Active-Passive DR solution can be achieved by replicating the metadata to keep the secondary namespace ready so that when the primary namespace is unavailable, the traffic can be directed to secondary namespace.
0 commit comments