microservices-patterns
Installation
SKILL.md
Microservices Patterns
Microservices split a system into small, independently deployable services, each owned by one team and owning its own data. The value is organizational: independent deploys, independent scaling, and a contained blast radius — but every one of those wins comes with a distributed-systems tax: cross-service consistency, partial failure, and contract drift. This skill is the playbook for paying that tax deliberately: deciding whether decomposition is warranted, finding the boundaries, and applying the canonical patterns for communication, consistency, resilience, observability, testing, and deployment.
Quick Reference
| Topic | Reference |
|---|---|
| Sagas, compensating actions, and the outbox pattern | saga-outbox.md |
| Timeouts, retries, circuit breakers, bulkheads, load shedding | resilience-patterns.md |
| Structured logs, RED metrics, OpenTelemetry tracing, health probes | observability-tracing.md |
Core Workflow
Use this sequence whenever you are architecting or re-architecting toward microservices: