4c2238dc45
Expand the conservative risk sync with explicit critical, offensive, and none patterns.\n\nAuto-apply high-confidence legacy label fixes, add the authorized-use notice when promoting offensive skills, and regenerate canonical and plugin artifacts so the unknown backlog keeps shrinking without loosening contributor input rules.
39 lines
1.3 KiB
Markdown
39 lines
1.3 KiB
Markdown
---
|
|
name: microservices-patterns
|
|
description: "Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems."
|
|
risk: none
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# Microservices Patterns
|
|
|
|
Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.
|
|
|
|
## Use this skill when
|
|
|
|
- Decomposing monoliths into microservices
|
|
- Designing service boundaries and contracts
|
|
- Implementing inter-service communication
|
|
- Managing distributed data and transactions
|
|
- Building resilient distributed systems
|
|
- Implementing service discovery and load balancing
|
|
- Designing event-driven architectures
|
|
|
|
## Do not use this skill when
|
|
|
|
- The system is small enough for a modular monolith
|
|
- You need a quick prototype without distributed complexity
|
|
- There is no operational support for distributed systems
|
|
|
|
## Instructions
|
|
|
|
1. Identify domain boundaries and ownership for each service.
|
|
2. Define contracts, data ownership, and communication patterns.
|
|
3. Plan resilience, observability, and deployment strategy.
|
|
4. Provide migration steps and operational guardrails.
|
|
|
|
## Resources
|
|
|
|
- `resources/implementation-playbook.md` for detailed patterns and examples.
|