microservices-patterns

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

4|1|Updated Mar 14, 2026

Search Tags:#architecture #api design #microservices #resilience #distributed systems #event-driven

Ready to run

npx skills add https://github.com/GPTtang/skill-atlas --skill microservices-patterns-gpttang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: microservices-patterns
Source: https://github.com/GPTtang/skill-atlas/tree/main/skills/devops/microservices-patterns
Command: npx skills add https://github.com/GPTtang/skill-atlas --skill microservices-patterns-gpttang

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive guide to designing and implementing microservices architectures, addressing challenges in service decomposition, communication, data management, and resilience.

Core Features & Use Cases

Service Decomposition: Learn strategies like business capability and subdomain-based decomposition.
Communication Patterns: Understand synchronous (REST, gRPC) and asynchronous (event-driven) communication.
Data Management: Implement patterns like "Database Per Service" and the Saga pattern for distributed transactions.
Resilience Patterns: Apply Circuit Breakers, Retries, and Bulkheads to build fault-tolerant systems.
Use Case: When breaking down a monolithic application into smaller, independent services, this Skill will guide you through choosing the right decomposition strategy and communication methods.

Quick Start

Use the microservices patterns skill to understand how to implement the Saga pattern for distributed transactions.

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 monolithic application into microservices?▼

To decompose a monolithic application into microservices, apply strategies based on business capabilities or subdomains. These decomposition strategies isolate domains to build smaller, independent services that can scale separately.

What is the best way to handle distributed transactions in microservices?▼

The best way to handle distributed transactions in microservices is implementing the Saga pattern. Combined with a database per service architecture, it manages data consistency across independent services without relying on distributed locks.

When should I use synchronous versus asynchronous communication in distributed systems?▼

Use synchronous communication like REST or gRPC when an operation requires immediate responses between services. Choose asynchronous event-driven communication in distributed systems when decoupling service execution and improving fault tolerance are the primary goals.

How do I build fault-tolerant microservices that handle network failures?▼

To build fault-tolerant microservices, apply resilience patterns like the circuit breaker to stop cascading failures, retries for transient network issues, and bulkheads to isolate failing components and protect critical system resources.

Does event-driven architecture work with the database per service pattern?▼

Yes, event-driven architecture works with the database per service pattern. Asynchronous events enable services to update their isolated databases independently while the saga pattern coordinates distributed data consistency across the system.