Update relational-vs-nosql-data.md
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:
For a distributed system to be continuously available, every request received by a non-failing node in the system must result in a response.
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
| 📄 File | 🔗 Preview link |
|---|---|
| docs/architecture/cloud-native/relational-vs-nosql-data.md | Relational vs. NoSQL data |
I'm using a corporate laptop and can't install nor lint. Can someone please help me?
@IEvangelist thanks for your suggestion and edit. I've committed them. Kindly please approve this PR.