{{ message }}
Replies: 2 comments
|
Having looked more closely at the problem, I assume you would have to implement some sort of raft solution, have writes happen on the main and simultaniously send the data to the read only nodes. If split, raft decides what any given location service can and cannot do. Then you have to manually handle the data sync after netsplit is over. |
0 replies
0 replies
Answer selected by
koculu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

ZoneTree does not provide a consensus algorithm, and you can use any algorithm that you wish.
ZoneTree provides opIndex to correctly order outgoing writes asynchronously. Depending on your algorithm choice, you may need the opIndex.
A simple Replicator class that replicates data to a secondary location is also in the repository:
https://github.com/koculu/ZoneTree/blob/main/src/ZoneTree/Core/Replicator.cs
https://github.com/koculu/ZoneTree/blob/main/src/ZoneTree.UnitTests/ReplicatorTests.cs