Compare And Swap (CAS) synchronization protocol #24
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
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.
This just moves https://hackmd.io/@gozala/w3-memory into RFC space. It is a sketch of the synchronization protocol providing Compare and Swap (CAS) semantics.
Primary intention here is to allow point to point synchronization with optimistic writes. It is inspired by git where you push changes but if head has changed you have to rebase (or merge) and then push. Except here we leverage prolly trees as it can represent complex state that can be efficiently synced between replicas without retaining complete history of changes. However if retaining history is desired that could still be done by encoding say merkle-clock in prolly tree at the top level or at individual entry level.