microservices-patternscommit 0f73766SKILL.md · Architecture Tuning
Microservices Patterns
Reference for microservice decomposition, sync and async communication, database-per-service, sagas, and resilience patterns like circuit breakers.
npx skills add wshobson/agents --skill microservices-patternsCommand selected. Copy it manually.
- Permissions
- read-repo
- write-files
- shell
- network
- Compatible with
- Claude Code, Codex, Cursor, Copilot, OpenCode
- GitHub
- 42.1k
- Source
- Community · Seth Hobson
- Status
- Scan passed
- License
- MIT
- Category
- Architecture Tuning
Core rule
Each service owns its data; no shared databases.
Execution Phases
Phase 01Decompose services
Split by business capability or DDD subdomain, or extract gradually from a monolith with the strangler fig pattern.
Phase 02Choose communication
Pick synchronous REST, gRPC or GraphQL versus async Kafka, queues or pub/sub, optionally behind an API gateway.
Phase 03Manage distributed data
Give each service its own database and use sagas with compensating actions for eventual consistency across services.
Phase 04Add resilience
Use circuit breakers to fail fast, retries with exponential backoff for transient faults, and bulkheads to isolate resources.
Permissions (summarised from SKILL.md)
| Capability | Needed | Details |
|---|---|---|
| File writes | Required | Writes service, event and saga code following the reference examples when implementing microservices. |
| Command execution | Not required | This is a design reference and does not ask to run commands. |
| Network outbound | Not required | Does not call external networks or services. |
SKILL.md frontmatter (YAML)
---
name: microservices-patterns
description: Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
---