distributed-systems

Distributed systems design requires applying fault-tolerance principles: define clear service boundaries, implement idempotent operations, set explicit timeouts and retry logic, and establish observability across all services. This skill provides structured templates to enforce these requirements in your architecture.

Data consistency in distributed systems depends on your coordination strategy. This skill guides you through consistency trade-offs, event-driven patterns, and multi-service coordination approaches to match your system's requirements and failure scenarios.

Use structured review templates to evaluate service boundaries, idempotency guarantees, timeout and retry configurations, and observability instrumentation. This skill provides review frameworks for microservices, event-driven, and distributed architectures to catch design gaps before deployment.

Event-driven architectures require planning for message ordering, idempotent consumers, failure recovery, and service decoupling. This skill covers event-driven design patterns and ensures you specify clear failure-handling strategies and observable event flows.

Distributed systems design is primarily a structured planning and review process, not tool-dependent. This skill provides best practices, design principles, and review templates you apply to your own architecture decisions regardless of specific technologies.

Fault tolerance requires explicit planning: timeouts prevent hanging requests, retries handle transient failures, idempotency ensures safe retries, and observability lets you detect problems. This skill enforces these requirements as mandatory design outcomes.