microservices-patterns

Decompose software into microservices with guidance for inter-service communication.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/selrai-company/claude-workshop-kit --skill microservices-patterns-selrai-company
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: microservices-patterns
Source: https://github.com/selrai-company/claude-workshop-kit/tree/main/skills/microservices-patterns
Command: npx skills add https://github.com/selrai-company/claude-workshop-kit --skill microservices-patterns-selrai-company

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designs and reasons about distributed systems by providing a structured collection of microservice patterns, helping teams plan boundaries, communication, and resilience.

Core Features & Use Cases

  • Decomposition guidance: bounded contexts, domain-driven design, strangler fig strategy for safe migration.
  • Communication patterns: synchronous REST/gRPC, asynchronous events, API gateway/BFF considerations, service discovery, circuit breakers, and bulkheads.
  • Saga and orchestration: orchestration and choreography approaches with explicit compensation workflows.
  • CQRS and Event Sourcing: write/read model separation and event-driven projections.
  • Anti-patterns and best practices: avoid distributed monoliths, shared databases, and fragile call chains.

Quick Start

Review a sample monolith, map bounded contexts, and outline an initial microservice boundary plan.

Frequently Asked Questions about microservices-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose a monolith into microservices using bounded contexts?

Microservices decomposition maps domain-driven bounded contexts to define service boundaries, applying the strangler fig strategy to safely migrate monolithic components into independent services without disrupting existing functionality.

What is the difference between saga orchestration and choreography in distributed systems?

Saga orchestration uses a central coordinator to manage transaction steps, while choreography relies on event-driven communication between services. Both approaches define explicit compensation workflows to handle failures across distributed service boundaries.

How do I implement CQRS and event sourcing for microservices?

CQRS separates write models from read projections in microservices, while event sourcing persists state changes as a sequence of events. Combined, they enable event-driven projections and scalable read/write operations across distributed systems.

What resilience patterns should I use for inter-service communication?

Microservices communication resilience relies on circuit breakers to prevent cascading failures and bulkheads to isolate resources. Additional patterns include API gateways, service discovery, and choosing between synchronous REST/gRPC or asynchronous events.

What are common microservices anti-patterns to avoid?

Common microservices anti-patterns include creating distributed monoliths with tight coupling, sharing databases across services, and building fragile call chains. Proper decomposition using bounded contexts and saga patterns prevents these architectural pitfalls.

When should I use an API gateway vs Backend for Frontend (BFF) in microservices?

API gateways centralize routing and cross-cutting concerns for microservices, while BFF patterns provide specialized interfaces for specific client applications. Choose based on whether you need generic routing or tailored response aggregation for different frontend experiences.