You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BePrepared should aim to act like a distributed write-ahead log essentially, the idea being that one node can begin a 'transaction' or operation, selecting 2 other available nodes to be the backup nodes as such.
In the event of the primary node/leader going down, another node which was selected will take over the operation.
Needs more thinking about a suitable solution to this problem. Should this be backed by something like a multi-raft solution, or is a custom state machine better?
The text was updated successfully, but these errors were encountered:
BePrepared should aim to act like a distributed write-ahead log essentially, the idea being that one node can begin a 'transaction' or operation, selecting 2 other available nodes to be the backup nodes as such.
In the event of the primary node/leader going down, another node which was selected will take over the operation.
Needs more thinking about a suitable solution to this problem. Should this be backed by something like a multi-raft solution, or is a custom state machine better?
The text was updated successfully, but these errors were encountered: