Consistency Coordination

This skill should be used when the user asks about the "CAP theorem", "PACELC", a "consistency model", "eventual vs strong consistency", "read-your-writes", "causal consistency", "quorum" or "R+W>N", "consensus", "Raft / Paxos", "leader election", "consistent hashing", a "distributed transaction", "2PC", or "saga". Use it whenever a design has multiple copies of data or coordinating nodes and a decision hinges on what a reader is guaranteed to see during replication lag, a network partition, or a node failure — even if the user doesn't say "consistency".

proyecto26 Updated 128 repo stars
system-design-skills — a memorized diagram breaks under a real constraint; the reasoning loop (clarify, estimate, compose, trade-offs, stress-test) composes 20

File contents

proyecto26/system-design-skills commit 1278a1a180

Frequently asked questions

npx get-skill add proyecto26/consistency-coordination