Scaling / HA using Raft / Multiraft about chai

[joeblew99]

https://github.com/BBVA/raft-badger

Looks promising..

[winwisely99]

This is a much preferred implementation of a raft framework.
It also supports the new pebble store

https://github.com/lni/dragonboat

[protosam]

To have a scalable system with raft, even multiraft, isn't very straight forward. There is quite a bit to consider. MIT 6.824: Distributed Systems can abridge some of this knowledge for anyone not in the know right now.

What should the FSM do? If it is only doing GET/PUT/DEL operations, the database is only highly available. This wont help with scaling data distribution or read/write scaling. It would only be useful as a locking system, from which coordination can be done in addition to.

Assuming that multiraft is used, one group would still need to maintain coordination of other groups. An entire system schema is necessary for that to work effectively.

The common problems to solve for multiraft are:

• how to handle coordination? (the answer is always some form of distributed locking and placement driver)
• scaling reads and writes (each group is fully replicated, think write amplification)
• handling transactions (sometimes these are partitioned to their own raft groups OR timestamping with 2Phase commits on top of MVCC)