microservices-patterns

Guide microservices architecture design with Python code examples for decomposition, communication, data, and resilience patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ACGSpgp/ACGS --skill microservices-patterns-acgspgp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: microservices-patterns
Source: https://github.com/ACGSpgp/ACGS/tree/main/.agent/workflows/backend-development/1.2.3/skills/microservices-patterns
Command: npx skills add https://github.com/ACGSpgp/ACGS --skill microservices-patterns-acgspgp

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides guidance and code examples for designing and implementing microservices architectures, addressing challenges in service decomposition, communication, data management, and resilience.

Core Features & Use Cases

  • Service Decomposition: Strategies like business capability and subdomain-based decomposition.
  • Communication Patterns: Examples for synchronous (REST, gRPC) and asynchronous (event-driven) communication.
  • Data Management: Patterns like Database Per Service and Saga for distributed transactions.
  • Resilience Patterns: Implementation of Circuit Breakers, Retries, and Bulkheads.
  • Use Case: When migrating a monolithic application to microservices, use this Skill to understand how to break down services, choose appropriate communication methods, and ensure data consistency and system resilience.

Quick Start

Use the microservices-patterns skill to design service boundaries for an e-commerce platform.

Frequently Asked Questions about microservices-patterns

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

FAQPage Schema
How do I design microservices service boundaries for a monolithic application?

Microservices service boundaries are designed using decomposition strategies like business capability and subdomain-based decomposition to break down monolithic applications into independent distributed services.

What is the Saga pattern for distributed data management in microservices?

The Saga pattern manages distributed data transactions across microservices by coordinating local database updates per service, ensuring data consistency without relying on a single shared database.

How do I implement Circuit Breaker and resilience patterns in distributed systems?

Resilience patterns like Circuit Breakers, Retries, and Bulkheads are implemented in distributed systems using provided Python code examples to prevent cascading failures and isolate service faults.

What is the best way to handle inter-service communication in microservices architecture?

Inter-service communication in microservices architecture is handled by choosing between synchronous methods like REST and gRPC or asynchronous event-driven communication based on your specific decoupling requirements.

When do I need the Database Per Service pattern in distributed systems?

The Database Per Service pattern is needed in distributed systems when you require independent scaling and data autonomy for each microservice, eliminating shared database bottlenecks during monolithic migrations.