microservices-patterns – Design & UI skill for AI agents
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
Install the microservices-patterns skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/microservices-patterns-a4000.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /microservices-patterns – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/microservices-patterns-a4000.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $microservices-patterns – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/microservices-patterns-a4000.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /microservices-patterns – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/microservices-patterns-a4000.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /microservices-patterns – then describe the task you want done.
SKILL.md content
Microservices Patterns
Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.
When to Use This Skill
- 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
Core Concepts
1. Service Decomposition Strategies
By Business Capability
- Organize services around business functions
- Each service owns its domain
- Example: OrderService, PaymentService, InventoryService
By Subdomain (DDD)
- Core domain, supporting subdomains
- Bounded contexts map to services
- Clear ownership and responsibility
Strangler Fig Pattern
- Gradually extract from monolith
- New functionality as microservices
- Proxy routes to old/new systems
2. Communication Patterns
Synchronous (Request/Response)
- REST APIs
- gRPC
- GraphQL
Asynchronous (Events/Messages)
- Event streaming (Kafka)
- Message queues (RabbitMQ, SQS)
- Pub/Sub patterns
3. Data Management
Database Per Service
- Each service owns its data
- No shared databases
- Loose coupling
Saga Pattern
- Distributed transactions
- Compensating actions
- Eventual consistency
4. Resilience Patterns
Circuit Breaker
- Fail fast on repeated errors
- Prevent cascade failures
Retry with Backoff
- Transient fault handling
- Exponential backoff
Bulkhead
- Isolate resources
- Limit impact of failures
Detailed patterns and worked examples
Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.
Related skills
- cpo-advisor – Product leadership for scaling companies. Product vision, portfolio strategy…
- mobile-android-design – Master Material Design 3 and Jetpack Compose patterns for building native Android apps…
- mobile-ios-design – Master iOS Human Interface Guidelines and SwiftUI patterns for building native iOS apps…
- impeccable – Frontend design guidance, upstream-maintained (impeccable).
- nextjs-app-router-patterns – Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and…
- inspecting-hermes-desktop-dom – Read the live Hermes desktop DOM/CSS over CDP.
- ip-as-logo – Design minimal cute IP mascot marks readable at 32px.
- openpiv – Performs Particle Image Velocimetry (PIV) analysis with OpenPIV. Use when extracting…