{
  "id": 20235622,
  "title": "Please Implement A Quorum Database",
  "url": "https://urgent.news/2026/11/15/please-implement-a-quorum-database",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-15T22:44:13.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://transactional.blog/talk/please-implement-a-quorum-database"
  },
  "original_language": "en",
  "account": "In this report, I will discuss the concept of quorum-based replication and its potential benefits for production databases. The speaker, who gave a presentation at HPTS 2026, argues that quorum replication is often overlooked in favor of Raft, despite its practicality. They highlight that only a small portion of databases in production actually utilize quorum-based replication, mostly OSS majority quorum databases and proprietary systems.\n\nThe speaker presents several examples of databases that have used quorums in the past, such as Voldemort, InfluxDB, Grafana Mimir, Weviate, Tencent PaxosStore, and CouchDB. However, they also note that some of these databases have since been re-architected or have limited use cases. They express disbelief that Cassandra, a well-known quorum database, is often considered the only good example of a quorum database.\n\nTo illustrate their point, the speaker creates a fictional database called CashDB, designed for splitting-the-bill with friends. They discuss the constraints of CashDB, such as limited operations and the need for high reliability. The speaker then explores different replication protocols to implement CashDB, including majority quorums, Raft, and E-Paxos.\n\nMajority quorums, like those used in Cassandra, offer fast write and read operations, but fail to provide a linearizable consistency model. The speaker argues that majority quorums may not be the best approach for CashDB, as they are better suited for eventual consistency scenarios. They instead propose considering Megastore's approach, which uses multi-Paxos without leader election to replicate logs for entities. However, they acknowledge that Paxos faces liveliness issues and latency spikes.\n\nThe speaker also briefly mentions E-Paxos, a variant of Paxos that allows for more selective consensus, but notes that it suffers from latency cliffs under contention. Ultimately, the speaker expresses a desire for more diverse examples of quorum databases in production, moving beyond the limited examples available.",
  "summary": null,
  "key_points": [
    "Quorum-based replication often overlooked in favor of Raft",
    "Examples of quorum databases: Voldemort, InfluxDB, Grafana Mimir",
    "CashDB proposal for splitting-the-bill with friends"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}