To be fair, many project's Raft implementations contained errors that can and had lead to data lost, so it's not all sunshine and roses.
IMHO, it's still easier to delegate the consensus problem to a third party service like Zookeeper or ETCD.
Raft is a large improvement over Paxos for practical implementations. But it's still tricky to get right. As far as I know, the only widely used, battle tested Raft implementation is github.com/hashicorp/raft. Which is why so many distributed systems are being built on golang over the last few years. I don't know if there is any Java raft implementation which has reached that level of maturity yet - but it seems like Confluence is trying with kraft.
Re:Kafka without ZooKeeper
by mavelikara on Wednesday March 31, 2021 @01:56AM
(#26643976)
What are the notable projects that implement Raft internally for leader election?
Also, do any of those projects publish their Raft implementation as a library for other projects to include?
After Raft, it became easier to just implement that layer yourself and so most projects after Raft (or probably more accurately once people started seeing how stable etcd was, ~2014), just used Raft internally where they would have previously used zookeeper.