Design and review microservices architectures with clear service boundaries.
npx skills add https://github.com/truongnat/skills --skill microservices-pro
Please help me install this Agent Skill. Skill: microservices-pro Source: https://github.com/truongnat/skills/tree/main/skills/microservices-pro Command: npx skills add https://github.com/truongnat/skills --skill microservices-pro
Designs and reviews microservices architectures with clearly bounded services and resilient interaction patterns.
Provide a boundary-first decomposition plan for your monolith into microservices with recommended ownership and interaction patterns.
High-intent search queries and answers about installing and using this skill.
To decompose a monolith into microservices, apply boundary-first decomposition principles to identify service ownership and data boundaries, reducing cross-service coupling. This yields a structured plan defining bounded contexts and interaction patterns for your distributed system.
The best resilience patterns for microservices architecture include circuit breakers, retries, and fallback strategies. Applying these interaction patterns maintains service availability and prevents cascading failures across distributed systems during partial outages.
Establish observability and governance for distributed systems by defining metrics, tracing, and deployment guardrails. This enables safe production deployments and ensures operational reliability across your microservices architecture.
Use domain-driven design for microservices decomposition when you need to define clear service boundaries and data ownership. It guides the separation of bounded contexts to minimize cross-service coupling during monolith decomposition.
Microservices architecture requires strict data ownership boundaries to reduce cross-service coupling. Identifying clear service boundaries ensures that each microservice independently manages its data, maintaining operational reliability across the distributed system.
AI-SafeterMap business domains into subdomains, bounded contexts, and a glossary.
JeffallanDecompose monoliths into microservices with domain-driven design and saga patterns.
CybLowDesign microservices with Saga orchestration, circuit breaker resilience, and 12-Factor practices.
KentoShimizuDefine modular monolith module boundaries and contracts within a single deployable unit.
