skills.rest
duanbiao2000
duanbiao2000COMMUNITY
Explore all skills by this author →
WebsiteGitHub

microservices-patterns

Design microservices architectures with service decomposition, event-driven communication, and resilience patterns.

3|1|Updated Feb 3, 2026
Search Tags:#architecture#microservices#ddd#resilience#event-driven#distributed-systems#service-boundaries
One-click install
npx skills add https://github.com/duanbiao2000/obsidianDoc26 --skill microservices-patterns-duanbiao2000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microservices-patterns
Source: https://github.com/duanbiao2000/obsidianDoc26/tree/main/agents-main/plugins/backend-development/skills/microservices-patterns
Command: npx skills add https://github.com/duanbiao2000/obsidianDoc26 --skill microservices-patterns-duanbiao2000

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured approach to designing and implementing complex microservices architectures by defining service boundaries, communication contracts, data ownership, and resilience patterns for distributed systems.

Core Features & Use Cases

  • Service decomposition strategies (by business capability, by subdomain with bounded contexts, and Strangler Fig pattern) to progressively split a monolith.
  • Communication patterns including synchronous REST/gRPC/GraphQL and asynchronous event-driven messaging for loose coupling.
  • Data management guidelines such as database per service and Saga-based distributed transactions for eventual consistency.
  • Resilience patterns like circuit breakers, retry with backoff, and bulkheads to isolate failures.
  • Service decomposition patterns with concrete examples showing multi-service collaboration (order, payment, inventory) and API gateway coordination.

Quick Start

Decompose a monolith into well-defined services using business boundaries, API contracts, and event-driven communication to enable independent deployment and resilience.

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 splits a monolith by business capability or subdomain using bounded contexts. The Strangler Fig pattern progressively extracts services, enabling independent deployment and scalable distributed systems.

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

Distributed transactions in microservices use the Saga pattern to maintain eventual consistency. Instead of two-phase commits, Sagas coordinate a sequence of local transactions with compensating actions to rollback failures.

How do circuit breakers and bulkheads improve microservices resilience?▼

Resilience patterns like circuit breakers prevent cascading failures by blocking calls to failing services, while bulkheads isolate resources to limit failure impact, ensuring distributed systems remain partially operational during outages.

When should I use event-driven communication over synchronous REST in microservices?▼

Event-driven communication in microservices uses asynchronous messaging to achieve loose coupling between services. Synchronous REST or gRPC is suitable for direct queries, while event-driven architectures handle complex, multi-service workflows.

How do I manage data ownership and databases in a microservices architecture?▼

Data ownership in microservices requires a database per service to ensure loose coupling. This pattern prevents services from sharing databases, enforcing data consistency through API contracts and event-driven updates.

Do I need an API gateway for service decomposition and multi-service collaboration?▼

An API gateway coordinates multi-service collaboration in distributed systems. It acts as a single entry point for clients, routing requests to decomposed services like order, payment, and inventory, while handling cross-cutting concerns.

Related Skills

Explore More Software Engineering Skills→
microsoftmicrosoft

design-philosophy-domain-driven

Analyze business domains to define bounded contexts and system boundaries.

Official
Advanced
mahg-esmahg-es
3

api-gateway

Design and configure API gateways for routing, authentication, and traffic management.

Official
Advanced
doanchienthangdevdoanchienthangdev
4

event-driven-architecture

Implement event sourcing, CQRS, and message queues with RabbitMQ and Kafka.

Community
Advanced
KentoShimizuKentoShimizu
7

architecture-monolith

Define modular monolith module boundaries and contracts within a single deployable unit.

Community
Advanced