Raft Consensus vs Practical Byzantine Fault Tolerance

Developers should learn Raft when building or working with distributed systems that require strong consistency, such as 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.

Raft Consensus

Nice Pick

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

Pros

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

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 Raft Consensus 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 Raft Consensus offers.

The Bottom Line

Raft Consensus wins

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