Muhammad Mansoor Afzal·2d agoMaking Durable Writes Work Without Stalling ConsensusInside a Paxos Library — Part 4: sharing disk flushes while preserving the meaning of every acknowledgement.A response icon1A response icon1
Muhammad Mansoor Afzal·Nov 9Why a Slow Load Must Never Overwrite a Newer WriteInside a Cache Library — Part 2: ordering explicit writes against loads already in flight.A response icon2A response icon2
Muhammad Mansoor Afzal·Nov 8Why Adding One Server Should Not Move Every KeyInside a Hash Library — Part 1: placing keys so servers can come and go without reshuffling everything.
Muhammad Mansoor Afzal·Nov 6What 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
Muhammad Mansoor Afzal·Oct 21Why 1,000 Cache Misses Should Trigger One LoadInside a .NET Cache — Part 1: coordinating concurrent requests before they become duplicate work.A response icon1A response icon1