Ayush Poddar's Wiki

      • Business
      • Financial philosophies and lessons
      • Investments and Personal Finance
      • Taxation
      • Documentation on some tools
      • Events, anecdotes and facts
      • Life Philosophies
      • Politics, governance and legals
      • Productivity
      • Climate change
      • High level designs - Software Systems
      • Industrial production
      • Software engineering

    Improve availability after failures - Using sloppy quorum

    Dec 16, 20241 min read

    Sloppy quorum

    Instead of enforcing the quorum requirement, the system chooses the first W healthy servers for writes and the first R healthy servers for reads. Offline servers are ignored.

    Related Notes

    • Using Quorum Consensus to get consistency

    Sources

    • (Done) Design A Key-value Store - Highlights

    Graph View

    • Sloppy quorum
    • Related Notes
    • Sources

    Backlinks

    • High level designs - Software Systems
    • Design a key-value store
    • Recover from permanent failures - Merkle Trees

    Created with Quartz v4.4.0 © 2024

    • GitHub
    • Discord Community