In Search of an Understandable Consensus Algorithm

By Diego Ongaro, John K. Ousterhout. USENIX Annual Technical Conference, 2014

2,803 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/9979809e4106b29d920094be265b33524cde8a40

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

A Comprehensive Review of Blockchain Consensus Mechanisms (2021, background): “To endure f faulty nodes in the blockchain network, raft requires the deployment of at least 2 f + 1 nodes within the network [132].”
The Honey Badger of BFT Protocols (2016, background): “While Paxos [33], Raft [42], and many other well-known protocols tolerate crash faults, Byzantine fault tolerant protocols (BFT), beginning with PBFT [20], tolerate even arbitrary (e.g., maliciously) corrupted nodes.”
The RAMCloud Storage System (2015, methodology): “There are currently two implementations of this interface, one based on ZooKeeper [Hunt et al. 2010] and the other based on LogCabin, a storage system that uses the Raft consensus protocol [GitHub 2015b; Ongaro and Ousterhout 2014].”
Verdi: a framework for implementing and formally verifying distributed systems (2015, methodology): “More details about Raft can be found in the original Raft paper [30] and Ongaro’s thesis [29].”
Towards Scaling Blockchain Systems via Sharding (2018, methodology): “ure work. Microsoft Coco [8] implements the entire consensus protocol in a trusted execution environment, reducing the failure model to crash failure. As a result, more ecient protocols such as Raft [51] and Paxos [38, 37] can be used. However, this approach incurs a much larger TCB than AHL+, makin”
Security and Privacy on Blockchain (2019, background): “In addition, the communication complexity of Paxos and Raft are much lower than that of PBFT, and they are easy to implement in practical systems.”
BLOCKBENCH: A Framework for Analyzing Private Blockchains (2017, background): “Zab [33], Raft [42], Paxos [35], PBFT [11] are popular protocols that are in active use today.”
A Byzantine Fault-Tolerant Ordering Service for the Hyperledger Fabric Blockchain Platform (2017, methodology): “Kadena [15] uses a variant of the Raft consensus protocol [22] adapted to Byzantine faults [23].”
CockroachDB: The Resilient Geo-Distributed SQL Database (2020, methodology): “We initially chose Raft as the consensus algorithm for CRDB due to its supposed ease of use and the precise description of its implementation [46].”
A Hitchhiker's Guide On Distributed Training of Deep Neural Networks (2018, methodology): “ity, All Reduce algorithms need to restarted in case of a machine failure. We propose a fault tolerant version of the binary blocks algorithm by incorporating elements of the Raft consensus algorithm [31] into the All Reduce. This algorithm is resilient to machine failures and continues execution as”
Untangling Blockchain: A Data Processing View of Blockchain Systems (2017, methodology): “Using Raft, Quorum is able to make safe progress even when some authority nodes crash.”
A Vademecum on Blockchain Technologies: When, Which, and How (2019, methodology): “The state machine replication (SMR) technique [59] enables the construction of fault-resilient consensus protocols; robust against crash failures in trusted environments (e.g., Paxos and RAFT [60, 61]) and additionally capable of tolerating Byzantine failures in networks of untrusted parties (e.g., ”
Faasm: Lightweight Isolation for Efficient Stateful Serverless Computing (2020, background): “FAASM’s global tier could be replaced with DSM to form a distributed object store, which would require a suitable consensus protocol, such as Raft [62], and a communication layer, such as Apache Arrow [65].”
zkLedger: Privacy-Preserving Auditing for Distributed Ledgers (2018, methodology): “Maintaining a fault-tolerant, globally ordered log is outside the scope of this paper, but can be done using standard techniques [15, 30, 39].”
Unmanned Aerial Vehicles for Search and Rescue: A Survey (2023, background): “The consensus of the distributed algo-rithm focuses on solving the consistency problem of the distributed systems, and the most famous one is the Raft algorithm [100], which is considered easy to understand in design and excellent in performance.”
Riposte: An Anonymous Messaging System Handling Millions of Users (2015, methodology): “To protect against benign failures, server maintainers could implement a single “logical” Riposte server with a cluster of many physical servers running a standard state-machine-replication protocol [54], [66].”
A Survey about Consensus Algorithms Used in Blockchain (2018, methodology): “3.2.2 Crash fault tolerance based consensus Motivated by the classical and difficult-to-understand consensus algorithm called Paxos [65], Raft [80] is a consensus algorithm that is used by Quorum [81] to tolerate crashes.”
ZEUS: Analyzing Safety of Smart Contracts (2018, methodology): “Permissioned blockchains do not typically use proof-based mining to reach a consensus since all the actors are known; instead they use consensus algorithms such as RAFT [72], Paxos [66] or PBFT [58] to achieve higher network throughput.”