Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
wshobson avatar

Microservices Patterns

  • 10.4k installs
  • 38.3k repo stars
  • Updated July 22, 2026
  • wshobson/agents

How do you architect distributed systems using microservices patterns including service boundaries, communication strategies, data management, and resilience mechanisms?

About

This skill teaches microservices architecture patterns for building distributed systems, including service decomposition strategies (business capability, DDD subdomains, strangler fig), communication approaches (REST, gRPC, GraphQL, Kafka, message queues), data management techniques (database per service, saga pattern for distributed transactions), and resilience patterns (circuit breaker, retry with backoff, bulkhead). Developers use this when decomposing monoliths, designing service boundaries, implementing inter-service communication, managing distributed data, or building systems requiring high availability and fault isolation.

  • Service decomposition by business capability, DDD subdomains, or strangler fig pattern for monolith extraction
  • Synchronous (REST, gRPC, GraphQL) and asynchronous (Kafka, RabbitMQ, SQS, Pub/Sub) communication patterns
  • Database per service design with saga pattern for distributed transactions and eventual consistency
  • Circuit breaker, retry with backoff, and bulkhead patterns for fault tolerance and cascade failure prevention
  • Service discovery, load balancing, and event-driven architecture implementation strategies

Microservices Patterns by the numbers

  • 10,450 all-time installs (skills.sh)
  • +199 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #80 of 4,386 Backend & APIs skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

microservices-patterns capabilities & compatibility

Capabilities
service decomposition strategy selection · communication pattern design and implementation · distributed data management and saga orchestrati · resilience pattern implementation (circuit break
Use cases
api development · devops
npx skills add https://github.com/wshobson/agents --skill microservices-patterns

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs10.4k
repo stars38.3k
Security audit3 / 3 scanners passed
Last updatedJuly 22, 2026
Repositorywshobson/agents

What it does

Design distributed system architectures by decomposing monoliths into services with event-driven communication and resilience patterns.

Who is it for?

Building scalable distributed systems, decomposing monoliths, designing event-driven architectures, implementing service-oriented infrastructure.

Skip if: Simple monolithic applications, single-server deployments, systems without inter-service communication requirements.

When should I use this skill?

Designing or refactoring multi-service architectures, establishing service boundaries, planning inter-service communication, hardening systems against network failures.

What you get

Developers can decompose systems into loosely-coupled services, implement resilient communication, manage distributed data, and prevent cascade failures.

  • Service boundary design documents
  • Communication protocol specifications
  • Resilience pattern implementations

By the numbers

  • Covers 4 core concept areas: service decomposition, communication patterns, data management, resilience patterns
  • Includes 3 decomposition strategies and 5+ named resilience patterns

Files

SKILL.mdMarkdownGitHub ↗

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.

Related skills

How it compares

Choose microservices-patterns over generic backend skills when the task is specifically splitting architectures and defining cross-service communication, not writing a single REST endpoint.

FAQ

What are the main service decomposition strategies?

By business capability (OrderService, PaymentService), by DDD subdomains (core vs supporting domains), or using strangler fig pattern to gradually extract from monolith.

When should I use synchronous vs asynchronous communication?

Use synchronous (REST, gRPC, GraphQL) for request/response when immediate response is required; use asynchronous (Kafka, RabbitMQ, Pub/Sub) for event streaming and decoupling services.

How do I handle transactions across multiple services?

Use saga pattern with compensating actions for distributed transactions, accepting eventual consistency instead of ACID guarantees.

Is Microservices Patterns safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Backend & APIsbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.