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".
Pinned to revision 228d57dc6fa7, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/consistency-coordination/SKILL.md
- skills/consistency-coordination/references/deep-dive.md
- skills/consistency-coordination/references/providers/aws.md
- skills/consistency-coordination/references/providers/gcp.md
- skills/consistency-coordination/references/providers/generic.md
Every link opens the file at its source, pinned to the revision this page describes.