This article explores the various consensus mechanisms available in Hyperledger Fabric, including PBFT, Kafka, Raft, Solo, and IBFT. It details their characteristics, use cases, and how they integrate with Fabric's architecture like ordering services and endorsement policies. A brief mention of Stellar Consensus Protocol (SCP) appears in the context of external consensus integration.
Hyperledger Fabric offers modular consensus mechanisms such as Practical Byzantine Fault Tolerance (PBFT), Kafka Orderer, Raft Orderer, Solo Orderer, and Istanbul BFT (IBFT), each suited for different enterprise needs like fault tolerance and scalability. The article explains how ordering service nodes use these mechanisms to order transactions, while peers handle endorsement and validation. Features like pluggable consensus, channels, and external integrations allow customization, including compatibility with protocols like Stellar's SCP via External Builders. Spydra leverages Fabric's Raft consensus for its blockchain solutions. The piece contrasts crash-fault tolerance (CFT) and Byzantine fault tolerance (BFT), advises on production choices, and covers FAQs on switching mechanisms and performance trade-offs.
