Skip to content

Conversation

@azarboon
Copy link
Contributor

@azarboon azarboon commented Jun 13, 2024

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

@dotnet-bot dotnet-bot added this to the June 2024 milestone Jun 13, 2024
@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates PR is created by someone from the .NET community. label Jun 13, 2024
@azarboon
Copy link
Contributor Author

I'm using a corporate laptop and can't install nor lint. Can someone please help me?

@azarboon
Copy link
Contributor Author

@IEvangelist thanks for your suggestion and edit. I've committed them. Kindly please approve this PR.

@BillWagner BillWagner merged commit f18fe13 into dotnet:main Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cloud-native/subsvc community-contribution Indicates PR is created by someone from the .NET community. dotnet-architecture/svc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants