Paxos vs Practical Byzantine Fault Tolerance

Developers should learn Paxos when building or working with distributed systems that require strong consistency, such as replicated state machines, distributed databases (e meets developers should learn pbft when building or working with high-assurance distributed systems, such as permissioned blockchains (e. Here's our take.

Paxos

Nice Pick

Developers should learn Paxos when building or working with distributed systems that require strong consistency, such as replicated state machines, distributed databases (e

Pros

• g
• Related to: distributed-systems, raft-consensus

Cons

• Specific tradeoffs depend on your use case

Practical Byzantine Fault Tolerance

Developers should learn PBFT when building or working with high-assurance distributed systems, such as permissioned blockchains (e

Pros

• g
• Related to: distributed-systems, consensus-algorithms

Cons

• Specific tradeoffs depend on your use case

The Verdict

Use Paxos if: You want g and can live with specific tradeoffs depend on your use case.

Use Practical Byzantine Fault Tolerance if: You prioritize g over what Paxos offers.

The Bottom Line

Paxos wins

Developers should learn Paxos when building or working with distributed systems that require strong consistency, such as replicated state machines, distributed databases (e