Skill

microservices-patterns

Provides microservices architecture patterns for service decomposition, communication, data management, resilience, and observability. Use for breaking down monoliths or designing distributed systems.

gRPC

REST API

backend

devops

npx claudepluginhub nickcrew/claude-cortex

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

Supporting Assets

references/communication-patterns.mdreferences/data-management.mdreferences/deployment-migration.mdreferences/observability.mdreferences/resilience-patterns.mdreferences/service-decomposition.mdvalidation/rubric.yaml

SKILL.md

Similar Skills

microservices-patterns

36.4k

Provides microservices architecture patterns for service boundaries, inter-service communication, data management, resilience, service discovery, and event-driven designs. Use for monolith decomposition and distributed systems.

1 file

antigravity-awesome-skills

microservices-patterns

682

Designs microservices architectures with service boundaries, event-driven communication, data management, and resilience patterns. Use for decomposing monoliths or building distributed systems.

1 file

rmyndharis-antigravity-skills

microservices

Guides microservices architecture: decompose monoliths, design service boundaries, implement sagas/CQRS/event sourcing, circuit breakers, API gateways, eventual consistency, resilience patterns, observability.

3 files1 tool

playbooks-virtuoso

Stats

Stars15

Forks6

Last CommitApr 23, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

Single Responsibility - Each service has one reason to change
Independent Deployability - No coordination required for deployments
Decentralized Data - Each service owns its data exclusively
Design for Failure - Embrace failures, build resilience
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

Distributed Monolith - Tightly coupled, must deploy together
Shared Database - Multiple services accessing same database
Chatty APIs - Excessive synchronous service calls
Missing Circuit Breakers - No cascading failure protection
No Observability - Deploying without tracing/logging/metrics
Ignoring Network Failures - Assuming reliable network
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