feat: replicated cache #16
Merged
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
* feat: implement wrapper client * feat: impl Client trait
As part of the replication, we'll need a version/generation number or similar in order to distinguish between later versions of a value on various remote stores. We can use the timestamp for this and the most recent (highest) value will win, i.e. last-write wins.
As part of the replication, we'll need a version/generation number or similar in order to distinguish between later versions of a value on various remote stores. We can use the timestamp for this and the most recent (highest) value will win, i.e. last-write wins.
…to feat/cache-replication
The initial implementation of this was slightly backwards with the naming. The ReplicationClient which also served requests does not make much sense. The better way to understand this is this commit entails, that is a ReplicatedServer which contains its own store and a client with an awareness of other server stores.
Need to fix deadlocks
Simplify to 3 nodes max for logic and try impl with futures Either/select functionality
Move to static node count within cluster
The replication with 3 `ReplicatedServer`'s is an infinite loop for retrieval and setting. The replication strategy should actually be a single server that is configured to replicate to other nodes, static to 2 for now.
jdockerty
force-pushed
the
feat/cache-replication
branch
from
1ef3038 to
b4a2847
Compare
jdockerty
force-pushed
the
feat/cache-replication
branch
from
b4a2847 to
b102616
Compare
Simplify architecture for replication mode such that we use a simple leader/follower model. Leader will simply replicate to followers. This can be altered in the future for smarter replication strategy or even distribution via consistent hashing etc.
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.
Closes #12
Supersedes #9 in terms of providing some sense of non-local caching to the project.
TODO
replicationcompilation flag should be enabled by default.