Claude Cursor Skill

microservices-patterns

Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.

LLM Mart · 0 points · 16 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_backend-development_skills_microservices-patterns-7e2fb55.zip · 4 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/backend-development/skills/microservices-patterns
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

Files (agents)
  • references
    • details.md 14.2 KB
      Loading…
  • SKILL.md 2.1 KB
    ---
    name: microservices-patterns
    description: Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
    ---
    
    # 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.
    
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.