Home

Introduction

Beaker is a distributed, transactional key-value store that is consistent and available. Beaker permits a minority of failures and hence it is N / 2 fault tolerant. Beaker assumes that failures are fail-stop. It makes no assumptions about the underlying network except that messages are received in the order they were sent. Most networking protocols, including TCP, satisfy this requirement.

Beaker uses a leader-less variation of Generalized Paxos to consistently execute transactions Beaker employs a variation of Paxos that has several desirable properties. First, beakers may simultaneously commit non-conflicting transactions. Second, beakers automatically repair replicas that have stale revisions. Third, beakers may safely commit transactions as long as they are connected to at least a majority of their non-faulty peers.

Contributors

• Ashwin Madavan: [email protected]
• Christopher J. Rossbach [email protected]