Rewrite the introduction to the Clustering section #2749
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NataliaIvakina
commented
Dec 2, 2025
NataliaIvakina
commented
Dec 2, 2025
modules/ROOT/pages/clustering/multi-region-deployment/geo-redundant-deployment.adoc
Show resolved
Hide resolved
NataliaIvakina
commented
Dec 2, 2025
NataliaIvakina
force-pushed
the
dev-update-clustering-intro
branch
from
6b095c3 to
87a6450
Compare
jackwaudby
reviewed
Dec 15, 2025
modules/ROOT/pages/clustering/multi-region-deployment/geo-redundant-deployment.adoc
Outdated
Show resolved
Hide resolved
| Servers and databases are decoupled: servers provide computation and storage power for databases to use. | ||
| Each database relies on its own cluster architecture, organized into primaries (with a minimum of three for high availability) and secondaries (for read scaling). | ||
| . *Fault tolerance:* Primary database allocations provide a fault tolerant platform for transaction processing. | ||
| A database remains available for reads and writes as long as a simple majority of its primary copies are functioning. |
Contributor
There was a problem hiding this comment.
Hmm depends actually, are we using copy/allocation interchangeably elsewhere? In which ignore this suggestion.
Contributor
There was a problem hiding this comment.
It might be good to use database allocation everywhere though.
Collaborator
Author
There was a problem hiding this comment.
In fact, we're using copies/allocations interchangeably. In the Disaster recovery, however, we decided to use allocations only.
Contributor
There was a problem hiding this comment.
I personally like the term allocation, but I will leave it at your discretion :)
NataliaIvakina
force-pushed
the
dev-update-clustering-intro
branch
from
87a6450 to
af0d43a
Compare
jackwaudby
reviewed
Dec 18, 2025
Collaborator
|
This PR includes documentation updates Updated pages: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rewrite the Clustering introductory page to include examples of database topologies.
Remove terminology inconsistencies across a few pages.