Skip to content
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

Wording around availability zones and multiple-region writes. #123628

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

FallenHoot
Copy link
Contributor

Multi-Region Writes don't support strong consistency, because you can't have an RTO/RPO of zero. Therefore, you can turn availability zones support on for multiple-region writes, but it adds minimal value.

Would need to be verified with PG/PMs if this should be grayed out in the Azure Portal to help with the confusion of this feature.

Copy link
Contributor

@FallenHoot : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit cdae558:

✅ Validation status: passed

File Status Preview URL Details
articles/reliability/reliability-cosmos-db-nosql.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Court72
Copy link
Contributor

Court72 commented Jul 4, 2024

@anaharris-ms

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jul 4, 2024
@seesharprun
Copy link
Contributor

seesharprun commented Jul 5, 2024

Any of these three individuals can review this pull request.

Copy link
Contributor

The following reviewer(s) could not be added because they aren't a valid GitHub ID, aren't a valid collaborator on this repo, or are the author of the PR: kanshigtheovankraayany of these three individuals can review this pull request.

@seesharprun
Copy link
Contributor

#assign-reviewer:kanshig

@seesharprun
Copy link
Contributor

#assign-reviewer:theovankraay

Copy link
Contributor

@TheovanKraay TheovanKraay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the suggestion. However, I don't quite understand its goal - the wording seems to be saying the same thing, but inverted to focus on multi-region writes, and now communicates less information (there are also single-region write scenarios where AZs add little value, as shown in the table below this sentence). It sounds like a customer was confused, can you articulate how they were confused, and how this wording will clarify for them?

@seesharprun
Copy link
Contributor

@FallenHoot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants