ddia-transactions-consistency
Skill1 starsChanged 6 months agoMITView on GitHub
Distilled knowledge from "Designing Data-Intensive Applications" (Kleppmann, 2nd ed.) chapters 8-10 on transactions, distributed system fundamentals, and consistency/consensus. Covers ACID semantics, weak/strong isolation, distributed failure modes, time/clocks, linearizability, and consensus protocols.
In this repository21 other files it gives its agents.
- ai-context-engineeringSkill
- ai-context-engine-productionSkill
- ai-context-engineSkill
- ai-dataset-engineeringSkill
- ai-evaluationSkill
- ai-finetuningSkill
- ai-foundation-modelsSkill
- ai-inference-optimizationSkill
- ai-multi-agent-mcpSkill
- ai-production-architectureSkill
- ai-prompt-engineeringSkill
- ai-rag-and-agentsSkill
- ai-rag-defenseSkill
- ddia-architectureSkill
- ddia-batch-stream-processingSkill
- ddia-data-ethicsSkill
- ddia-data-modelingSkill
- ddia-replication-shardingSkill
- job-description-analyzerSkill
- resume-content-writerSkill
- resume-fit-scorerSkill
The file
Files
DDIA Transactions and Consistency
A reference skill covering the safety properties of single-node transactions (chapter 8) and the additional difficulties that distributed systems impose on those properties (chapters 9-10). Organized into 9 categories that can be loaded individually as needed.
Quick Start
- Open
guidelines.mdto find which files match your task or symptom - Load only the listed files — most tasks need 1-3 reference files
- For a multi-step process (e.g., picking an isolation level), check
workflows/instead
Contents
References
| Category | Files | Purpose |
acid-fundamentals/ | knowledge, rules, examples | What ACID actually means; transaction model basics |
isolation-levels/ | knowledge, rules, examples | Read committed, snapshot isolation, lost updates, write skew |
serializability/ | knowledge, rules, examples | Serial execution, 2PL, SSI |
distributed-transactions/ | knowledge, rules, examples | 2PC, XA, atomic commit across nodes |
distributed-failures/ | knowledge, rules, examples | Partial failure, network partitions, faults |
distributed-time/ | knowledge, rules, examples | Wall vs monotonic clocks, NTP, process pauses |
distributed-truth/ | knowledge, rules, examples | Quorums, leases, fencing tokens, system models |
linearizability/ | knowledge, rules, examples | Strong consistency, CAP, logical clocks |
consensus/ | knowledge, rules, examples | Paxos/Raft, ZooKeeper, etcd, leader election |
Workflows
| Task | Workflow |
| Choose database isolation level (read committed, snapshot, serializable) | workflows/choosing-isolation-level.md |
| Diagnose a distributed bug (lost write, stale read, race condition) | workflows/diagnosing-distributed-bug.md |
| Design a fault-tolerant distributed system | workflows/designing-fault-tolerant-system.md |
| Choose consensus / coordination tool (ZooKeeper, etcd, Consul) | workflows/choosing-consensus-tool.md |
Guidelines
See guidelines.md for:
- Task-based file selection (transaction design, concurrency bugs, distributed coordination, failure modes)
- Symptom/question lookup ("two updates raced and one was lost", "clock skew causing weird ordering", etc.)
- Topic index across all 9 categories
- Decision trees for isolation level, consensus tool, and distributed lock design
- Complete file index (27 reference files)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.