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: modules/ROOT/pages/clustering/multi-region-deployment/geo-redundant-deployment.adoc
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,12 @@
2
2
[role=enterprise-edition]
3
3
4
4
5
-
= Designing a resilient multi-data center Neo4j cluster
5
+
= Design a resilient multi-data center cluster
6
6
7
7
[[multi-region-deployment-overview]]
8
8
== Overview
9
9
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.
11
11
12
12
You should take into account cluster architecture and topology and decide where database primaries and secondaries are located, balancing performance and fault tolerance.
13
13
@@ -19,10 +19,10 @@ If primaries are far apart, network latency adds to commit time.
19
19
20
20
21
21
[[recommended-cluster-patterns]]
22
-
== Recommended Neo4j cluster design patterns
22
+
== Recommended cluster design patterns
23
23
24
24
[[secondaries-for-read-resilience]]
25
-
=== Use database secondaries for read resilience
25
+
=== Read resilience with user database secondaries
26
26
27
27
image::secondaries-for-read-resilience.svg[width="400", title="Cluster design with database secondaries for better read performance", role=popup]
28
28
@@ -56,7 +56,7 @@ For detailed scenarios, see the xref:clustering/multi-region-deployment/disaster
56
56
57
57
58
58
[[geo-distributed-dc]]
59
-
=== Use geo-distributed data centers
59
+
=== Geo-distribution of user database primaries
60
60
61
61
image::geo-distributed-primaries.svg[width="400", title="Cluster design with primaries distributed across three data centers", role=popup]
62
62
@@ -86,7 +86,7 @@ For detailed scenarios, see the xref:clustering/multi-region-deployment/disaster
86
86
87
87
88
88
[[geo-distribution-system-database]]
89
-
=== Use full geo-distribution for the `system` database only
89
+
=== Exclusive geo-distribution for the `system` database
90
90
91
91
image::geo-distribution-system-db.svg[width="400", title="Primaries for the `system` database distributed across three data centers", role=popup]
92
92
@@ -122,7 +122,7 @@ You need to accept a smaller topology that fits in the remaining data center.
0 commit comments