Skip to content

Commit 1058aa6

Browse files
committed
Acrolinx
1 parent ebe4012 commit 1058aa6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/api-management/high-availability.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Azure [availability zones](../availability-zones/az-overview.md) are physically
2929

3030
Enabling [zone redundancy](../availability-zones/migrate-api-mgt.md) for an API Management instance in a supported region provides redundancy for all [service components](api-management-key-concepts.md#api-management-components): gateway, management plane, and developer portal. Azure automatically replicates all service components across the zones that you select.
3131

32-
When you enable zone redundancy in a region, consider the number of API Mangement scale [units](upgrade-and-scale.md) that need to be distributed. Minimally, configure the same number of units as the number of availability zones, or a multiple so that the units are distributed evenly across the zones. For example, if you select 3 availability zones in a region, you could have 3 units so that each zone hosts one unit.
32+
When you enable zone redundancy in a region, consider the number of API Management scale [units](upgrade-and-scale.md) that need to be distributed. Minimally, configure the same number of units as the number of availability zones, or a multiple so that the units are distributed evenly across the zones. For example, if you select 3 availability zones in a region, you could have 3 units so that each zone hosts one unit.
3333

3434
> [!NOTE]
3535
> Use the [capacity](api-management-capacity.md) metric and your own testing to decide on the number of scale units that will provide the gateway performance for your needs. Learn more about [scaling and upgrading](upgrade-and-scale.md) your service instance.
@@ -67,11 +67,11 @@ API Management provides an SLA of 99.99% when you deploy at least one unit in tw
6767
6868
## Backend availability
6969

70-
Depending on where and how your backend services are hosted, you may need to set up redundant backends in different regions to meet your requirements for service availability. You can manage backend failover through API Management to maintain availability. For example:
70+
Depending on where and how your backend services are hosted, you may need to set up redundant backends in different regions to meet your requirements for service availability. You can manage regional backends and handle failover through API Management to maintain availability. For example:
7171

7272
* In multi-region deployments, use [policies to route requests](api-management-howto-deploy-multi-region.md#-route-api-calls-to-regional-backend-services) through regional gateways to regional backends.
7373

74-
* Configure policies to route requests conditionally to different backends in case of backend failure in a particular region.
74+
* Configure policies to route requests conditionally to different backends if there is backend failure in a particular region.
7575

7676
* Use caching to reduce failing calls.
7777

0 commit comments

Comments
 (0)