All issues

[distributed-systems/2PC] Clarify ACID, 2PL, WAL, atomic commit, and coordinator failure

#173

· elimelt opened

on Aug 4, 2026

[distributed-systems/scaling-web-services] Modernize the architecture note around failure domains, caching, and service boundaries

#171

· elimelt opened

on Aug 4, 2026

[distributed-systems/sharding] Add placement algorithms, rebalancing, hotspots, and routing correctness

#172

· elimelt opened

on Aug 4, 2026

[distributed-systems/paxos-made-simple] Add a formal safety proof, recovery model, and executable trace

#169

· elimelt opened

on Aug 4, 2026

[distributed-systems/primary-backup] Add a complete view-service protocol, client deduplication, and split-brain fencing

#170

· elimelt opened

on Aug 4, 2026

[distributed-systems/paxos-intro] Separate FLP, consensus, leader election, and replicated-log mechanics

#168

· elimelt opened

on Aug 4, 2026

[distributed-systems/paxos-architecture] Add a practical architecture comparison for Paxos, leases, and coordination services

#167

· elimelt opened

on Aug 4, 2026

[distributed-systems/event-ordering] Repair the Lamport-clock note and separate logical order from physical time

#166

· elimelt opened

on Aug 4, 2026

[distributed-systems/non-blocking-2PC] Explain Paxos Commit precisely and separate it from ordinary 2PC

#165

· elimelt opened

on Aug 4, 2026

[distributed-systems/mutual-exclusion] Complete the distributed-lock algorithm and prove its assumptions

#164

· elimelt opened

on Aug 4, 2026

[distributed-systems/managing-critical-state] Split the malformed note into CAP, consensus, and coordination fundamentals

#163

· elimelt opened

on Aug 4, 2026

[distributed-systems/load-balancing] Replace the queueing and popularity sketches with a precise load-balancing guide

#162

· elimelt opened

on Aug 4, 2026