consensus-basics
/consensus-basics
Wyjaśnia, co zapewniają Raft i Paxos, arytmetykę kworum i kiedy konsensus jest w ogóle potrzebny.
- Autor
- Amey-Thakur ↗
- Repozytorium
- AI-SKILLS ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 05.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 05.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wyjaśnia, co zapewniają Raft i Paxos, arytmetykę kworum i kiedy konsensus jest w ogóle potrzebny.
Oryginalny opis (EN)
Understand what Raft and Paxos actually provide, quorum arithmetic, and when you need consensus at all. Use when deploying replicated coordination systems or deciding whether a problem truly requires consensus.
Jak działa
- Method
- Boundaries
Podgląd SKILL.md
--- name: consensus-basics description: Understand what Raft and Paxos actually provide, quorum arithmetic, and when you need consensus at all. Use when deploying replicated coordination systems or deciding whether a problem truly requires consensus. --- # Consensus basics Consensus makes a cluster of unreliable machines agree on one ordered log of decisions. It is the foundation under leader election, unique ids, and configuration stores, and it is expensive: use it for decisions, not for data. ## Method 1. **Know what the protocol gives you.** Raft/Paxos provide: a single agreed sequence of entries, surviving minority failure, with a leader through whom writes flow. They do not provide: performance at scale, multi-cluster agreement, or safety with a majority down. 2. **Do the quorum math before sizing.** N nodes tolerate floor((N-1)/2) failures: 3 nodes survive 1, 5 survive 2. Even counts add cost without tolerance (4 still survives only 1); more than 5 voters slows every write for marginal gain. Across three zones: 3 or 5 voters spread so no zone holds a majority. 3. **Respect the failure modes that remain.** A minority partition cannot elect a leader and stalls (by design; see partition-tolerance). Clock-independent safety means correctness holds, but liveness suffers under flapping networks and long GC pauses: leadership churns and writes stall. Watch election counts as a health metric. 4. **Use consensus for coordination, not data.** Store: configuration, membership, locks, leader leases, small critical metadata (etcd, ZooKeeper, Consul model). Do not store: application data, queues, large blobs; every byte is replicated through the leader and fsynced into the log. 5. **Prefer rented consensus.** Managed control planes, or building on an existing store's primitives (compare-and-swap, leases), beat embedding a Raft library, which beats implementing a paper. The protocols are proven; the operational surface (snapshots, membership change, disk behavior) is where deployments fail. 6. **Verify liveness assumptions in tests.** Kill leaders under load, partition the minority and the majority, pause a node with SIGSTOP through an election. What the docs promise and what your configuration delivers meet only in these drills. ## Boundaries - If a single coordinator with failover-and-fencing suffices (one scheduler, one migration runner), a lease from an existing store (see distributed-locks, leader-election) beats running your own consensus cluster. - Consensus does not order events across independent clusters or regions; that requires either one stretched quorum (latency) or application-level reconciliation. - Byzantine failures (lying nodes) are outside Raft/Paxos scope entirely; that is BFT territory with different protocols and costs.
Wersje
W bazie nie ma innych skilli o nazwie consensus-basics.
Migawka bazy z 13.11.2026 · wersja paczki 55dc65aed8fa (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90distributed-consensus
Opisuje architekturę systemów rozproszonych na poziomie protokołów: konsensus (Raft, Paxos, BFT), replikację i kworum, modele spójności, synchronizację zegarów oraz kompromisy CAP i PACELC. - 100distributed-consensus-reliability
Ocenia konsensus rozproszony pod kątem niezawodności: kiedy stosować systemy typu Paxos lub Raft, tryby awarii i ryzyka operacyjne. - 100distributed-consensus
Wyjaśnia konsensus i replikację: kworum, odporność na awarie, Raft, Paxos, wybór lidera, dzierżawy i tokeny fencingu. - 100consistency-coordination
Wyjaśnia modele spójności i koordynacji w systemach rozproszonych: CAP i PACELC, quorum, Raft i Paxos, elekcja lidera, consistent hashing, transakcje rozproszone, 2PC i saga. - 100distributed-systems-interviewer
Wciela się w teoretycznego rozmówcę typu Distinguished Engineer, który odpytuje z systemów rozproszonych: twierdzenie CAP, PACELC, konsensus (Raft, Paxos), skew zegarów, zegary wektorowe i split-brain. - 100paxos-webhooks
Odbiera i uwierzytelnia webhooki Paxos, konfiguruje klucz API i obsługuje zdarzenia tożsamości, wpłat kryptowalut i zleceń.