Ac Consensus Protocols

How a distributed system agrees on one order of events: the replicated log as the agreement object, leaders and term-and-index structure, quorum intersection and what a commit proves, leader leases and fencing tokens, membership changes and joint configurations, single-decree epochs, learner and witness roles, and the written record. It explains what a consensus commits and what it costs; it never recommends a protocol library and never promises a fault-free cluster. Use when asking "consensus protocol", "raft", "paxos", "replicated log", "commit index", "leader lease", "fencing token", "membership change", "joint consensus", "learner node", "why is my cluster stalled", "quorum intersection", "log compaction". Not for leader election alone (ac-distributed-state-and-replication), not for client-side session guarantees (ac-distributed-state-and-replication), not for queue delivery semantics (ac-durable-execution).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit 6ac636a531

Frequently asked questions

npx get-skill add jiayaoqijia/ac-consensus-protocols