distributed-systems
Reason about cross-service consistency, replication, partitioning, consensus, time, failure detection, retries, timeouts, circuit breakers, idempotency, ambiguous outcomes, multi-region recovery and capacity. Use when a design or incident depends on behavior across process, network or region boundaries; architecture decisions, service contracts, fault experiments and telemetry stay with their owning activities.
Pinned to revision c37715f7cf0d, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/distributed-systems/SKILL.md
- skills/distributed-systems/references/failure-and-consistency.md
- skills/distributed-systems/references/resilience-checklist.md
Every link opens the file at its source, pinned to the revision this page describes.