HN2new | past | comments | ask | show | jobs | submitlogin

Hmmm that sorta makes sense I guess. Sorta because raft is a replication algorithm. If you don't use raft in datapath you don't get any of its guarantees


Most data paths don't need consensus for replication. You can implement ACID Transactions on top of many other replication algorithms for example. Ultimately the choice comes down to read/write ratios. Chain Replication has much better read throughout than Paxos and Raft.


I see. What's the catch though. Sounds like free lunch. Is there some gotcha with partition tolerance?


It’s the case of 2F+1 versus F+1. Paxos/Raft offer fault tolerance where as other replication algorithms don’t. If you have a node failure in Primary-Backup or Chain for example you need to reconfigure before committing more writes. However in practice and certain environments reconfiguration can be faster than or the same as a leader failure in Paxos that requires running Phase 1 again.


Got it, makes sense. To the extent this can be formalized, I feel this is a much better alternative than consensus based approaches




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: