microservice-patterns

Guide microservices design with decomposition, communication, and resilience patterns.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/zangxin75/openclaw-skills --skill microservice-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: microservice-patterns
Source: https://github.com/zangxin75/openclaw-skills/tree/main/microservice-patterns
Command: npx skills add https://github.com/zangxin75/openclaw-skills --skill microservice-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to designing and implementing microservices, helping developers avoid common pitfalls like the "distributed monolith" anti-pattern and build robust, scalable systems.

Core Features & Use Cases

  • Decomposition Strategies: Learn how to break down monoliths into business-capability-aligned services using patterns like Strangler Fig.
  • Communication Patterns: Understand synchronous (REST/gRPC) and asynchronous (event-driven) communication, including resilience techniques like retries and circuit breakers.
  • Data Management: Explore database-per-service and distributed transaction patterns like Saga.
  • Resilience & API Gateway: Implement circuit breakers, bulkheads, and API gateways for fault tolerance and a unified entry point.
  • Use Case: When migrating a monolithic application to microservices, this Skill guides the team on service boundaries, communication protocols, and data consistency strategies.

Quick Start

Use the microservice-patterns skill to understand the Saga pattern for distributed transactions.

Frequently Asked Questions about microservice-patterns

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

FAQPage Schema
How do I manage distributed transactions in microservices?

Implement resilient inter-service communication using circuit breakers, bulkheads, and retries. These patterns prevent cascading failures by stopping requests to unavailable services and isolating fault domains.

What is the best way to decompose a monolith into microservices?

Decompose a monolith using the Strangler Fig pattern to incrementally replace legacy components. Align service boundaries with business capabilities to avoid the distributed monolith anti-pattern and ensure maintainability.

When do I need an API Gateway in a microservices architecture?

Use an API Gateway when you need a unified entry point for client requests. It handles request routing, composition, and protocol translation, simplifying client access to underlying microservices.

How does the Saga pattern handle data consistency across services?

The Saga pattern handles data consistency through event-driven compensating transactions. If a step fails, compensating actions undo prior changes, maintaining eventual consistency across distributed databases.

Synchronous REST vs asynchronous event-driven microservices communication?

Use the database-per-service pattern to decouple data storage. This pattern ensures each service manages its own database, preventing direct data coupling and allowing independent scaling.