Skip to content

Commit d99ac13

Browse files
Polishing headings
1 parent d77cf01 commit d99ac13

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

modules/ROOT/pages/clustering/multi-region-deployment/geo-redundant-deployment.adoc

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,12 @@
22
[role=enterprise-edition]
33

44

5-
= Designing a resilient multi-data center Neo4j cluster
5+
= Design a resilient multi-data center cluster
66

77
[[multi-region-deployment-overview]]
88
== Overview
99

10-
Deploying a resilient multi-data center cluster, the goal is to achieve high availability, disaster recovery, and tolerance against the loss of a data center.
10+
The goal of deploying a resilient multi-data center cluster is to achieve high availability, disaster recovery, and tolerance against the loss of a data center.
1111

1212
You should take into account cluster architecture and topology and decide where database primaries and secondaries are located, balancing performance and fault tolerance.
1313

@@ -19,10 +19,10 @@ If primaries are far apart, network latency adds to commit time.
1919

2020

2121
[[recommended-cluster-patterns]]
22-
== Recommended Neo4j cluster design patterns
22+
== Recommended cluster design patterns
2323

2424
[[secondaries-for-read-resilience]]
25-
=== Use database secondaries for read resilience
25+
=== Read resilience with user database secondaries
2626

2727
image::secondaries-for-read-resilience.svg[width="400", title="Cluster design with database secondaries for better read performance", role=popup]
2828

@@ -56,7 +56,7 @@ For detailed scenarios, see the xref:clustering/multi-region-deployment/disaster
5656

5757

5858
[[geo-distributed-dc]]
59-
=== Use geo-distributed data centers
59+
=== Geo-distribution of user database primaries
6060

6161
image::geo-distributed-primaries.svg[width="400", title="Cluster design with primaries distributed across three data centers", role=popup]
6262

@@ -86,7 +86,7 @@ For detailed scenarios, see the xref:clustering/multi-region-deployment/disaster
8686

8787

8888
[[geo-distribution-system-database]]
89-
=== Use full geo-distribution for the `system` database only
89+
=== Exclusive geo-distribution for the `system` database
9090

9191
image::geo-distribution-system-db.svg[width="400", title="Primaries for the `system` database distributed across three data centers", role=popup]
9292

@@ -122,7 +122,7 @@ You need to accept a smaller topology that fits in the remaining data center.
122122

123123

124124
[[cluster-anti-patterns]]
125-
== Neo4j cluster design patterns to avoid
125+
== Cluster design patterns to avoid
126126

127127

128128
[[two-dc-unbalanced-membership]]

0 commit comments

Comments
 (0)