-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs 824 arch overview #6405
Open
jpe442
wants to merge
12
commits into
develop
Choose a base branch
from
DOCS-824-arch-overview
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Docs 824 arch overview #6405
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
Add this label to a PR and it will automatically be deployed to netlify
label
Jan 14, 2025
jpe442
force-pushed
the
DOCS-824-arch-overview
branch
from
January 14, 2025 17:59
bd8ddf0
to
4289842
Compare
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.
What Changed?
New PGD Architecture Overview section to replace the Basic Architecture section we have now.
Originally started in this PR, but got a bit too out of sync with the base branch.
Critical feedback from Petr I tried to answer in the Architectural Flexibility section:
"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)."