What problem does it solve? Designing microservices architectures is error-prone: poorly drawn service boundaries create distributed monoliths, missing resilience patterns cause cascading failures, and lack of observability makes production debugging nearly impossible. This Skill provides a structured architecture workflow with validation checkpoints at every stage. ## Core Features & Use Cases - Domain-Driven Decomposition: Identify bounded contexts and service boundaries using DDD, with guidance on the strangler fig pattern for monolith migration. - Communication & Data Design: Choose between REST, gRPC, GraphQL, message queues, and event streams; apply database-per-service, saga, event sourcing, and CQRS patterns. - Resilience & Observability: Implement circuit breakers, retries with jitter, bulkheads, health probes, correlation IDs, distributed tracing, and SLO-based alerting. - Use Case: When decomposing a monolithic e-commerce application, use this Skill to map bounded contexts (orders, payments, inventory), design an orchestrated saga for checkout, and define readiness probes and tracing for each new service. ## Quick Start Ask the assistant to design a microservices architecture for your system, including service boundaries, communication patterns, and resilience strategies.
