aa71e76eb9
- Add date_added to all 950+ skills for complete tracking - Update version to 6.5.0 in package.json and README - Regenerate all indexes and catalog - Sync all generated files Features from merged PR #150: - Stars/Upvotes system for community-driven discovery - Auto-update mechanism via START_APP.bat - Interactive Prompt Builder - Date tracking badges - Smart auto-categorization All skills validated and indexed. Made-with: Cursor
39 lines
1.4 KiB
Markdown
39 lines
1.4 KiB
Markdown
---
|
|
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 micros..."
|
|
risk: unknown
|
|
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.
|