Back to catalog / Developer tools
Microservice boundaries and resilience design
Decompose around business boundaries and plan communication, data ownership, and failure isolation.
Skills
Define service boundaries from business capabilities and bounded contexts rather than technical layers, with one owner for each data domain. Choose REST/gRPC, queues, or event streams according to query and consistency needs; add idempotency, compensations, timeouts, backoff, and isolation. Extract from a monolith incrementally behind proxy routes, and document contracts, data ownership, and failure propagation.
Permissions
Prerequisites
- Needs domain, call-flow, and data-ownership context; no cloud provider is assumed.
Permissions
- May inspect architecture/contracts/config and propose boundary or resilience changes; review database, routing, or deployment changes separately.
Limitations
Microservices add operational and consistency costs; validate patterns against actual load and failure objectives.
Pinned upstream source
- Repository
- wshobson/agents
- File path
- plugins/backend-development/skills/microservices-patterns/SKILL.md
- Pinned commit
46891e7e60da0e52baf1050b7b6391b64e84c6d9- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Claude Code · compatible coding agents
Main topic
Take a coding Agent change from context to verification