Skip to content
Skillv1.0.0

microservices-patterns

Comprehensive microservices architecture patterns covering service decomposition, communication, data management, and resilience strategies. Use when designing distributed systems, breaking down monol

by nickcrew(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from nickcrew/claude-cortex (skills/microservices-patterns/SKILL.md). Install upstream with npx skills add nickcrew/claude-cortex --skill microservices-patterns. Copyright stays with the author.

Microservices Architecture Patterns

Expert guidance for designing, implementing, and operating microservices architectures.

When to Use This Skill

  • Breaking down monolithic applications into services
  • Designing distributed systems from scratch
  • Implementing service communication patterns (sync/async)
  • Managing data consistency across services
  • Building resilient distributed systems
  • Defining service boundaries and API contracts

Core Principles

  1. Single Responsibility - Each service has one reason to change
  2. Independent Deployability - No coordination required for deployments
  3. Decentralized Data - Each service owns its data exclusively
  4. Design for Failure - Embrace failures, build resilience
  5. Automate Everything - Deployment, scaling, and recovery

Quick Reference

Load detailed patterns on-demand:

Task Load Reference
Define service boundaries and decompose monoliths skills/microservices-patterns/references/service-decomposition.md
Implement service communication (sync/async) skills/microservices-patterns/references/communication-patterns.md
Manage data consistency and transactions skills/microservices-patterns/references/data-management.md
Build resilient systems (circuit breakers, retries) skills/microservices-patterns/references/resilience-patterns.md
Add observability (tracing, logging, metrics) skills/microservices-patterns/references/observability.md
Plan deployments and migrations skills/microservices-patterns/references/deployment-migration.md

Workflow

1. Understand Requirements

  • Map business capabilities and domains
  • Assess scalability/resilience needs
  • Identify team boundaries

2. Define Service Boundaries

Load references/service-decomposition.md for:

  • Business capability decomposition
  • DDD bounded contexts
  • Service boundary validation

3. Design Communication

Load references/communication-patterns.md for:

  • Synchronous: API Gateway, REST, gRPC
  • Asynchronous: Message Queue, Pub/Sub, Event Sourcing

4. Manage Data

Load references/data-management.md for:

  • Database per service pattern
  • Saga distributed transactions
  • CQRS read/write optimization

5. Build Resilience

Load references/resilience-patterns.md for:

  • Circuit breakers
  • Retry with exponential backoff
  • Bulkhead isolation
  • Rate limiting and timeouts

6. Add Observability

Load references/observability.md for:

  • Distributed tracing
  • Centralized logging
  • Metrics and monitoring

7. Plan Deployment

Load references/deployment-migration.md for:

  • Blue-Green, Canary, Rolling deployments
  • Strangler Fig migration pattern

Common Mistakes

  1. Distributed Monolith - Tightly coupled, must deploy together
  2. Shared Database - Multiple services accessing same database
  3. Chatty APIs - Excessive synchronous service calls
  4. Missing Circuit Breakers - No cascading failure protection
  5. No Observability - Deploying without tracing/logging/metrics
  6. Ignoring Network Failures - Assuming reliable network
  7. No API Versioning - Breaking changes without versioning

Fixes: Load relevant reference files for detailed solutions.

Resources

  • Books: "Building Microservices" (Newman), "Microservices Patterns" (Richardson)
  • Sites: microservices.io, martinfowler.com/microservices
  • Tools: Kubernetes, Istio, Kafka, Kong, Jaeger, Prometheus

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/nickcrew-claude-cortex-microservices-patterns/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

nickcrew-claude-cortex-microservices-patterns.ocm.jsonjson
{
  "ocm": "1",
  "id": "nickcrew-claude-cortex-microservices-patterns",
  "kind": "skill",
  "name": "microservices-patterns",
  "description": "Comprehensive microservices architecture patterns covering service decomposition, communication, data management, and resilience strategies. Use when designing distributed systems, breaking down monoliths, or implementing service-to-service communication.",
  "publisher": "nickcrew",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "api-gateway",
      "circuit-breaker",
      "distributed-system",
      "inter-service-communication",
      "microservices",
      "saga-pattern",
      "service-decomposition",
      "service-discovery",
      "service-mesh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Comprehensive microservices architecture patterns covering service decomposition, communication, data management, and resilience strategies. Use when designing distributed systems, breaking down monoliths, or implementing service-to-service communication."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/nickcrew/claude-cortex",
      "path": "skills/microservices-patterns/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/nickcrew/claude-cortex/blob/HEAD/skills/microservices-patterns/SKILL.md",
      "key": "nickcrew/claude-cortex/skills/microservices-patterns/SKILL.md"
    }
  },
  "instructions": "# Microservices Architecture Patterns\n\nExpert guidance for designing, implementing, and operating microservices architectures.\n\n## When to Use This Skill\n\n- Breaking down monolithic applications into services\n- Designing distributed systems from scratch\n- Implementing service communication patterns (sync/async)\n- Managing data consistency across services\n- Building resilient distributed systems\n- Defining service boundaries and API contracts\n\n## Core Principles\n\n1. **Single Responsibility** - Each service has one reason to change\n2. **Independent Deployability** - No coordination required for ",
  "cost": {
    "context_tokens": 865
  }
}

Fetch it by URL: GET /api/v1/registry/nickcrew-claude-cortex-microservices-patterns/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.