The building blocks of consensus

Authors:
Yee Jiun Song;Robbert van Renesse;Fred B. Schneider;Danny Dolev
Affiliations:
Cornell University;Cornell University;Cornell University;The Hebrew University of Jerusalem
Venue:
ICDCN'08 Proceedings of the 9th international conference on Distributed computing and networking
Year:
2008

Citing 11
Cited 1

The consensus problem in fault-tolerant computing

ACM Computing Surveys (CSUR)
Impossibility of distributed consensus with one faulty process

Journal of the ACM (JACM)
Unreliable failure detectors for reliable distributed systems

Journal of the ACM (JACM)
The Load, Capacity, and Availability of Quorum Systems

SIAM Journal on Computing
The part-time parliament

ACM Transactions on Computer Systems (TOCS)
Reaching Agreement in the Presence of Faults

Journal of the ACM (JACM)
The Byzantine Generals Problem

ACM Transactions on Programming Languages and Systems (TOPLAS)
Another advantage of free choice (Extended Abstract): Completely asynchronous agreement protocols

PODC '83 Proceedings of the second annual ACM symposium on Principles of distributed computing
A Generic Framework for Indulgent Consensus

ICDCS '03 Proceedings of the 23rd International Conference on Distributed Computing Systems
Byzantine quorum systems

Distributed Computing
The Alpha of Indulgent Consensus

The Computer Journal

Selected results from the latest decade of quorum systems research

Replication

Quantified Score

Hi-index	0.00

Visualization

Abstract

Consensus is an important building block for building replicated systems, and many consensus protocols have been proposed. In this paper, we investigate the building blocks of consensus protocols and use these building blocks to assemble a skeleton that can be configured to produce, among others, three well-known consensus protocols: Paxos, Chandra-Toueg, and Ben-Or. Although each of these protocols specifies only one quorum system explicitly, all also employ a second quorum system. We use the skeleton to implement a replicated service, allowing us to compare the performance of these consensus protocols under various workloads and failure scenarios.