Microservices Patterns

Apply proven microservices patterns including saga, circuit breaker, bulkhead, and eventual consistency. Use when designing service-to-service communication and handling distributed failures.

48 stars 10 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill microservices-patterns
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/system-design/skills/microservices-patterns ~/.claude/skills/microservices-patterns

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Microservices Patterns

Master distributed system patterns that enable loose coupling, resilience, and independent deployability across service boundaries.

## Context

You are an architect designing microservices interactions. The user is facing challenges around service-to-service communication, distributed transactions, or resilience. Read their current architecture and pain points.

## Domain Context

Based on Chris Richardson's Microservices Patterns and Sam Newman's work:

- **Saga Pattern**: Coordinate distributed transactions without 2PC; break into choreography (event-driven) or orchestration (central coordinator)
- **Circuit Breaker**: Fail fast when downstream service is unavailable; prevent cascading failures
- **Bulkhead Pattern**: Isolate thread pools/resources per service to prevent one slow service from impacting others
- **Eventual Consistency**: Accept stale reads at service boundaries; couple through events, not synchronous calls
- **Idempotency Keys**: Every operation is idempotent; safe to retry without duplicating side effects

## Instructions

1. **Map Distributed Transactions**: Identify workflows crossing service boundaries (e.g., payment → inventory → shipping). For each, decide: synchronous (API call) or asynchronous (events)?

2. **Choose Saga Style**: If async needed, choose choreography (services emit events, others listen) or orchestration (central coordinator). Choreography is loose coupling; orchestration is easier to debug.
Read the full skill on GitHub

Details

Skill name
microservices-patterns
Path
architect/system-design/skills/microservices-patterns/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Microservices Patterns skill do?

Apply proven microservices patterns including saga, circuit breaker, bulkhead, and eventual consistency. Use when designing service-to-service communication and handling distributed failures.

How do I install the Microservices Patterns skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Microservices Patterns popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.