ddia-replication-sharding
Skill1 starsChanged 6 months agoMITView on GitHub
Distilled guidance from "Designing Data-Intensive Applications" (Kleppmann, 2nd ed) chapters 6-7 on replication topologies, sharding strategies, conflict resolution, and request routing for distributed data systems.
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-transactions-consistencySkill
- job-description-analyzerSkill
- resume-content-writerSkill
- resume-fit-scorerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Read guidelines.md to find the right reference file(s) for your task.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
DDIA Replication & Sharding
A reference skill covering the design space for replicated and sharded data systems, drawn from Martin Kleppmann's "Designing Data-Intensive Applications" (2nd edition), chapters 6-7. Use it when picking a replication topology, deciding a partition key, planning rebalancing, choosing a conflict resolution policy, or designing secondary indexes that span shards.
Quick Start
- Read
guidelines.mdto find the right reference file(s) for your task. - Load only the files relevant to your scenario (most tasks need 1-3 files).
- For multi-step design tasks, see the
workflows/directory. - Apply the rules and patterns to your specific system.
Contents
References
| Category | Files | Purpose |
single-leader-replication/ | knowledge, rules, examples | Primary-backup, sync vs async, lag, failover, replication log formats |
multi-leader-replication/ | knowledge, rules, examples | Multi-region, sync engines, offline-capable clients, topology choices |
conflict-resolution/ | knowledge, rules, examples | Avoidance, LWW, CRDTs, OT, manual resolution, concurrency detection |
leaderless-replication/ | knowledge, rules, examples | Dynamo-style, quorums, read repair, sloppy quorums, vector clocks |
sharding-strategies/ | knowledge, rules, examples | Range vs hash partitioning, hot spots, rebalancing, multitenancy |
routing-and-secondary-indexes/ | knowledge, rules, examples | Request routing, local vs global secondary indexes, ZooKeeper-style coordination |
Workflows
| Task | Workflow |
| Choose replication topology (single-leader, multi-leader, leaderless) | workflows/choosing-replication-topology.md |
| Design a sharding scheme (key, strategy, hot-spot mitigation) | workflows/designing-sharding-scheme.md |
| Handle write conflicts (LWW, CRDT, OT, manual) | workflows/handling-replication-conflicts.md |
Guidelines
See guidelines.md for:
- Task-based file selection (replication design, conflict strategy, sharding design, index design)
- Symptom-based lookup (stale reads, hot keys, multi-region latency, etc.)
- Topic-by-topic file index
- Decision tree for replication and sharding strategy
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.