kalilurrahman/kr-claudiator-skills/geo-distributed-systems
Claude Code and agent skill by kalilurrahman/kr-claudiator-skills
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Design systems that serve users globally with low latency. Outputs data placement strategy, consistency model, region routing, and conflict resolution approaches.
Install
npx vskill@latest install kalilurrahman/kr-claudiator-skills/geo-distributed-systemsSKILL.md
Geo-Distributed Systems
Distributing a system globally is not just deploying to multiple regions. It requires data placement decisions (where data lives), routing decisions (which region serves a request), consistency decisions (how regions stay in sync), and conflict resolution (what happens when concurrent writes collide).
Architecture Patterns
Data Placement Strategy
Region Routing
Conflict Resolution (CRDTs)
Anti-Patterns to Avoid
| Anti-Pattern | Problem | Fix | |
|---|---|---|---|
| Assuming low latency cross-region | US to EU is 70-100ms baseline | Design for async; don't synchronously wait cross-region | |
| Strong consistency everywhere globally | Requires cross-region consensus — very slow | Eventual consistency for non-critical; strong only where required | |
| Ignoring data residency | GDPR violation for EU data outside EU | Map data types to residency requirements | |
| Active-active without conflict resolution | Concurrent writes corrupt data | Choose: LWW, vector clocks, or application-specific CRDTs | |
| No region failover | Region outage takes down global service | Automatic traffic shifting on region health failure |
10 Rules
- Data residency requirements are non-negotiable — map them before designing data placement.
- Cross-region latency is 50-200ms — design async; never block on cross-region calls.
- Active-active requires a conflict resolution strategy — decide upfront, not after the first conflict.
- Follow-the-sun routing reduces latency for globally distributed user bases.
- Global data (product catalog, reference data) is replicated; user data follows the user.
- GeoDNS is the first routing layer — steer users to the nearest healthy region.
- Test region failover quarterly — untested failover is not failover.
- Eventual consistency is the reality for active-active — design the application to accept it.
- User's "home region" is determined at account creation — moving it is a migration, not a config change.
- Cross-region writes are expensive — minimise them; batch where possible.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryChecking06-system-design/geo-distributed-systems/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kalilurrahman/kr-claudiator-skills/geo-distributed-systems)