Paxos made live: an engineering perspective

By Tushar Chandra, Robert Griesemer, Joshua Redstone. ACM SIGACT-SIGOPS Symposium on Principles of Distributed Computing, 2007

752 citations recorded by the source corpus.

Subfields: Computer Networks and Communications, Information Systems

View Paper: https://www.semanticscholar.org/paper/76aad5b272219c6745c76b7874129797e97e6041

How researchers see this paper

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

In Computer Networks and Communications

In Information Systems

Citations in the corpus

Site Reliability Engineering: How Google Runs Production Systems (2016, background): “In practice, however, ignoring a failed node may correspond to timeouts, retries, and other failure-handling approaches beneath the particular Paxos implementation [Cha07].”
Trinity: a distributed graph engine on a memory cloud (2013, methodology): “For applications that need transaction support, we can implement light-weight atomic operation primitives that span multiple cells, such as MultiOp primitives [13] and Mini-transaction primitives [7], on top of the atomic cell operation primitives.”
Gorilla: A Fast, Scalable, In-Memory Time Series Database (2015, methodology): “Within each region, a Paxos-based [6, 14] system called ShardManager assigns shards to nodes.”
Bigtable: a distributed storage system for structured data (2006, methodology): “Chubby uses the Paxos algorithm [9, 23] to keep its replicas consistent in the face of failure.”
Mnemosyne: lightweight persistent memory (2011, neutral): “Categories and Subject Descriptors D.4.2[Operating Systems]: Storage Management; D.4.5 [Operating Systems]: Reliability; D.4.8[OperatingSystems]:Performance General Terms Design,Languages,Performance,Reliability Keywords Persistentmemory, storage-class memory,persistence, memory transactions,perf”
Tendermint: Byzantine Fault Tolerance in the Age of Blockchains (2016, background): “Unfortunately, there was little work on improving the problem framing to make it more understandable, though there were efforts to delineate solutions to the various difficulties [18].”
In Search of an Understandable Consensus Algorithm (2014, methodology): “proven protocol [2].”
Megastore: Providing Scalable, Highly Available Storage for Interactive Services (2011, background): “Megastore defines a data model that lies between the abstract tuples of an RDBMS and the concrete row-column storage of NoSQL.”
Blockchain Consensus Protocols in the Wild (2017, methodology): “The Chubby database of Google [24] and Yahoo!’s ZooKeeper [38], developed for synchronizing critical conﬁguration information across data centers, support strong consistency and high availability through redundancy and tolerate benign failures and network outages.”
Distributed SDN Control: Survey, Taxonomy, and Challenges (2018, methodology): “In particular, Paxos [77] is used for detecting and handling the primary controller failure within each data-center site by electing a new leader controller among a set of reachable standby instances.”
ZooKeeper: Wait-free Coordination for Internet-scale Systems (2010, neutral): “In fact, as Chubby [8], we keep a replay log (a write-ahead log, in our case) of committed operations and generate periodic snapshots of the in-memory database.”
Bigtable: A Distributed Storage System for Structured Data (2008, methodology): “Chubby uses the Paxos algorithm [9, 23] to keep its replicas consistent in the face of failure.”
The Quest for Scalable Blockchain Fabric: Proof-of-Work vs. BFT Replication (2015, neutral): “Historically, state-machine replication protocols, and in particular their BFT variants, have been recognized as very challenging to design and implement [11, 5, 3].”
Zab: High-performance broadcast for primary-backup systems (2011, background): “Previous systems have been designed to coordinate long-lived and infrequent application state changes [9], [10], [11].”
There is more consensus in Egalitarian parliaments (2013, methodology): “Production implementations optimize this process using snapshots [7].”
Mencius: Building Efficient Replicated State Machine for WANs (2008, positive): “Recent examples of services that use replicated state machines include Chubby [6, 8], ZooKeeper [37] and Boxwood [28].”