Curious, why Paxos over Raft?
SDPaxos: Building efficient semi-decentralized geo-replicated state machines
11–14 of 14 posts
Re: SDPaxos: Building efficient semi-decentralized geo-replicated state machines
#12Curious, why Paxos over Raft?
Note that there's 3-10 variants of Paxos depending on who you ask and how many research papers you've read. Paxos has different performance characteristics, different implementations, and more maturity. There is no simple answer to your question unless you make it more specific.
I am no expert on Paxos - just hoping for an explanation.
Re: SDPaxos: Building efficient semi-decentralized geo-replicated state machines
#13Re: SDPaxos: Building efficient semi-decentralized geo-replicated state machines
#14Earlier quoted context omitted.
Note that there's 3-10 variants of Paxos depending on who you ask and how many research papers you've read. Paxos has different performance characteristics, different implementations, and more maturity. There is no simple answer to your question unless you make it more specific.
Considering we’re talking about distributed state-machines, I am curious why you would choose Paxos, a more complex algorithm over Raft. Raft, to my knowledge provides the same guarantees as Paxos, and is simpler to understand and implement. I am no expert on Paxos - just hoping for an explanation.
Where it get complicated is trying to build a practical replicated log system using Paxos. Raft just happen to clearly and completely define this use case.
What SDPaxos or EPaxos try to achieve is good performance over WAN. Something that Raft and any Paxos variant that rely on a stable leader are very bad at.
This can’t be easily added to raft because the main reason the raft algorithm is simpler is because it assume a stable leader in every operation except leader election.