Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
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
Identify domain boundaries and ownership for each service.
Define contracts, data ownership, and communication patterns.
Plan resilience, observability, and deployment strategy.
Provide migration steps and operational guardrails.
Resources
resources/implementation-playbook.md for detailed patterns and examples.
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.