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

Consistency level #134

Open
slowfranklin opened this issue May 26, 2023 · 0 comments
Open

Consistency level #134

slowfranklin opened this issue May 26, 2023 · 0 comments
Assignees
Labels
question Further information is requested

Comments

@slowfranklin
Copy link

What consistency level do you implement? For linearizable read and writes based on a quorum logic, reads must do write repair and writes must do pre-read. Your architecture docs are a bit sparse on this topic. Also, for distributed locking you need atomic-compare-and-swap which can't be implemented by a quorum based architecture as this requires consensus. As the article mentions Junodb is used for distributed locking, I wonder if the architecture description of Juno is missing important pieces.

@varuntechie varuntechie added the question Further information is requested label Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants