What problem does it solve? Designing distributed systems is error-prone: unclear service boundaries, fragile inter-service calls, and distributed transaction failures can derail a microservices migration. This Skill provides proven architecture patterns and working code examples to guide those decisions. ## Core Features & Use Cases - Service Decomposition: Split monoliths by business capability, DDD subdomains, or the Strangler Fig pattern with clear ownership boundaries. - Communication Patterns: Implement synchronous REST/gRPC calls with retries, or asynchronous event-driven messaging with Kafka producers and consumers. - Data & Resilience: Apply database-per-service, Saga orchestration for distributed transactions, and circuit breakers with retry/backoff and bulkhead isolation. - Use Case: When decomposing a monolithic e-commerce app, use the Saga pattern example to coordinate order creation, inventory reservation, and payment processing with compensating actions on failure. ## Quick Start Ask the AI to design a microservices architecture for your system, including service boundaries, event-driven communication, and circuit breaker resilience patterns.
