5 ms·

What are of the shelve solutions when it comes to actually using these protocols? Implementing these in-house doesn't make sense to me.

• jluxenberg 6y ago
  `etcd` is probably the canonical off-the-shelf solution. Other implementations are listed here https://raft.github.io/#implementations https://raft.github.io/#implementations
• kitotik 6y ago
  Consul[0] and Nomad [1] by HashiCorp both use raft. [0] https://consul.io https://consul.io [1] https://nomadproject.io https://nomadproject.io
  • jaquers 6y ago
    As does RabbitMQ, Docker Swarm, AlertManager (prometheus addon). If you run any of these systems in production, it is good to have a cursory understanding.
• b203 6y ago
  Zookeeper is the standard one which has been around the oldest. Zookeeper is not based on raft, but it has similar semantics as etcd. So if you don't care about the impl, ZK may be good as well.
  • ra7 6y ago
    The Zookeeper consensus algorithm is called Zookeeper Atomic Broadcast (ZAB).
• q3k 6y ago
  If you want a library and not a fully-fledged raft-backed KV daemon/service, there's also dragonboat [1]. [1] - https://github.com/lni/dragonboat https://github.com/lni/dragonboat
• skunkworker 6y ago
  YugabyteDB https://blog.yugabyte.com/how-does-the-raft-consensus-based-replication-protocol-work-in-yugabyte-db/ https://blog.yugabyte.com/how-does-the-raft-consensus-based-... And CockroachDB both use raft consensus https://www.cockroachlabs.com/docs/stable/architecture/replication-layer.html https://www.cockroachlabs.com/docs/stable/architecture/repli...