Muhammad Mansoor Afzal·5d agoWhat a Paxos Node Must Remember After a CrashInside a Paxos Library — Part 3: preserving promises, accepted commands, and recoverable history across process failure.
Muhammad Mansoor Afzal·Oct 29How Nodes Agree on One Ordered Command HistoryInside a Paxos Library — Part 2: following a command from proposal to majority agreement and ordered delivery.
Muhammad Mansoor Afzal·Oct 21Why I Built a Multi-Paxos Library for .NETInside a Paxos Library — Part 1: turning agreement, application state, and failure into explicit architectural boundaries.A response icon1A response icon1
Nick Athanassiadis·Oct 1Paradise Wasn’t Built for AugustWhy can it be so difficult to find fresh local fish and a really good tomato on a Greek island?
Nick Athanassiadis·Sep 30Never Pick a Fight With a Retired GreekI have some free advice for corporations everywhere.
Goutham Kalla·Sep 3Ever Wonder Why RDMA Doesn’t Make Your Database Faster?You have a distributed transaction that takes 60 milliseconds to commit. You profile it. Most of the time is “network.” So you do the…
Abdul Moiz·Jul 27Consensus Algorithm | Raft & Paxos, Explained SimplyIf your service has ever gone down and come back up somewhere else without you doing anything, some algorithm made that decision for you…
InInterviewNoodlebyArslan Ahmad·Jul 25Paxos vs. Raft: Distributed Consensus ExplainedThe two algorithms that underpin every strongly-consistent distributed system — what they solve, how they differ, and why one became the…
InOceanBase DatabasebyOceanBase·Jul 6Permanent Server Offline in OceanBase: How the Cluster Heals After a Node Is GoneAn OceanBase cluster runs every log stream on three (or more) replicas coordinated by Paxos. When one of those replicas goes down — an…
InOceanBase DatabasebyOceanBase·Jun 18Zero Data Loss, Fast Failover: How OceanBase Uses Multi-Paxos for High AvailabilityIt’s 3 a.m. A node in your database cluster goes dark. The on-call engineer has two questions, in this order: Did we lose any committed…
