Update relational-vs-nosql-data.md #43234
Open
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
azarboon
requested review from
nishanil,
IEvangelist and
a team
as code owners
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.
Summary
The page mainly explains CAP theorem and just briefly mentions PACELC theorem and leaves it to reader to pursue it further. I'm afraid that's not how it should be. Marc Brooker is one of thought leaders in database field. In this blog post, he explains why CAP theorem is outdated a bit, and it's relevant for intermittent environments such as IoT and for distributed environments, PACELC theorem should be considered, instead. I've made an edit.
Fixes #Issue_Number (if available)
Internal previews