Replaces Basic Architecture section in PGD Overview page with an enhanced architecture overview #5966
Conversation
This file contains 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
jpe442
added
the
deploy
github-actions
bot
temporarily deployed
to
pr-5966-pgd-5-overview-docs-824
github-actions
bot
temporarily deployed
to
pr-5966-pgd-5-overview-docs-824
github-actions
bot
temporarily deployed
to
pr-5966-pgd-5-overview-docs-824
github-actions
bot
temporarily deployed
to
pr-5966-pgd-5-overview-docs-824
github-actions
bot
temporarily deployed
to
pr-5966-pgd-5-overview-docs-824
github-actions
bot
temporarily deployed
to
pr-5966-pgd-5-overview-docs-824
github-actions
bot
temporarily deployed
to
pr-5966-pgd-5-overview-docs-824
djw-m
reviewed
Oct 16, 2024
github-actions
bot
temporarily deployed
to
pr-5966-pgd-5-overview-docs-824
PJMODOS
reviewed
Nov 9, 2024
|
|
||
| Nodes apply data in the order in which commits were made on the source node, ensuring transactional consistency is guaranteed for the changes from any single node. Changes from different nodes are applied independently of other nodes to ensure the rapid replication of changes. | ||
| #### Node types and roles |
There was a problem hiding this comment.
Can we not mix those? This way it looks like write leader is distinct node type, that's confusing and misleading.
PJMODOS
reviewed
Nov 9, 2024
|
|
||
| ### High availability | ||
| ### Architectural aims |
There was a problem hiding this comment.
I kind of hate that we put this into HA topic, I much prefer us talking about flexibility, which high availability is just effect/result of.
I.e. flexibility in:
- rolling maintenance operations (blue/green)
- postgres minor/major upgrades
- system upgrades
- schema changes
- vacuum
- automated failover and self-healing (node coming back after failure/disconnect automatically reconnects to cluster and continues working)
- selective replication
- configurable durability (commit scopes)
- multiple write nodes
- read scaling with SO nodes
The text under mentions most of this, but it's all talking about HA which limits the scope of things IMO (i.e. it does not leave space for things like commit scopes).
Also, I would like to remove discussion about logical standbys as much as possible, we don't want to encourage use of those, if anything we want to discourage use of those.
github-actions
bot
temporarily deployed
to
pr-5966-pgd-5-overview-docs-824
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
DOCS-824
Replaces Basic Architecture section in PGD Overview page with an enhanced architecture overview.