Update relational-vs-nosql-data.md #41422
Merged
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
I'm afraid the current definition is technically incorrect. Following is the exact definition coined by Gilbert and Lynch in their paper, section 2.2:
So, I've replaced it.
Also, many people, including my former past, mistakenly thought that "availability" in cap theorem means "highly available" system. Unfortunately, this mistaken belief is prevalent. I would highly suggest reading this blog post. I tried to add a gist of it, in a simple language, to warn the readers so they won't have false expectations.
Also if you are looking for academic work, this paper has touched the topic, too. Though there are more resources if you Google.
Fixes #Issue_Number (if available)
Internal previews