Skip to content

Commit 31e3503

Browse files
committed
Edits for readability
1 parent fb9d614 commit 31e3503

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

articles/search/search-reliability.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -16,11 +16,12 @@ ms.custom: subject-reliability, references_regions
1616
Across Azure, *reliability* means maintaining resiliency and availability if there's a service outage or degradation. In Cognitive Search, reliability is achieved when you:
1717

1818
+ Configure a service to use multiple replicas, paired with availability zone support.
19+
1920
+ Deploy multiple search services across different geographic regions.
2021

21-
All workloads are fully contained within a single service that runs in a single geographic region. Within a region, you can configure search to use multiple replicas that run in different availability zones.
22+
All search workloads are fully contained within a single service that runs in a single geographic region. Within a region, you can configure search to use multiple replicas that run in different availability zones.
2223

23-
For business continuity and disaster recovery, you should develop a strategy that includes a cross-regional architecture, consisting of multiple search services having identical configuration and content. Your custom script or code provides the "fail over" mechanism to an alternate search service if one suddenly becomes unavailable.
24+
For business continuity and recovery from disasters at a regional level, you should develop a strategy that includes a cross-regional architecture, consisting of multiple search services having identical configuration and content. Your custom script or code provides the "fail over" mechanism to an alternate search service if one suddenly becomes unavailable.
2425

2526
<a name="scale-for-availability"></a>
2627

@@ -81,13 +82,11 @@ Availability Zones don't impact the [Azure Cognitive Search Service Level Agreem
8182

8283
## Multiple services in separate geographic regions
8384

84-
Although most customers use just one service, service redundancy might be necessary if operational requirements include the following:
85+
Service redundancy is necessary if operational requirements include:
8586

8687
+ [Business continuity and disaster recovery (BCDR)](../availability-zones/cross-region-replication-azure.md) (Cognitive Search doesn't provide instant failover in the event of an outage).
8788

88-
+ Globally deployed applications. If query and indexing requests come from all over the world, users who are closest to the host data center will have faster performance. Creating additional services in regions with close proximity to these users can equalize performance for all users.
89-
90-
+ [Multi-tenant architectures](search-modeling-multitenant-saas-applications.md) sometimes call for two or more services.
89+
+ Global availability. If query and indexing requests come from all over the world, users who are closest to the host data center will have faster performance. Creating additional services in regions with close proximity to these users can equalize performance for all users.
9190

9291
If you need two or more search services, creating them in different regions can meet application requirements for continuity and recovery, as well as faster response times for a global user base.
9392

0 commit comments

Comments
 (0)