Skip to content

proyecto26/system-design-skills

v0.1.0MIT

A divide-and-conquer wiki of system-design skills. Reason about a design problem one part at a time -- requirements, capacity, APIs, storage, caching, load balancing, messaging, consistency, resilience, delivery, and scaling -- each with generic recipes, cloud-provider variants (AWS/Azure/GCP/Temporal), explicit trade-offs, and failure-mode analysis. Optimizes for reasoning over memorized architectures.

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".

Read SKILL.md at the source

Pinned to revision 228d57dc6fa7, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.