microservices-patterns

Apply microservices patterns to decompose monoliths and define service boundaries.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill microservices-patterns-leonardoteodoroo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microservices-patterns
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/microservices-patterns
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill microservices-patterns-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps teams design distributed systems by establishing service boundaries, choosing appropriate inter-service communication patterns, and applying resilience patterns to improve reliability and scalability.

Core Features & Use Cases

  • Service decomposition strategies across business capabilities and domains (DDD)
  • Synchronous and asynchronous communication patterns for reliable integration
  • Data ownership, per-service boundaries, and Saga-based transaction patterns
  • Resilience patterns such as circuit breakers, retries, and bulkhead isolation
  • Guidance for implementing service discovery, load balancing, and observability

Quick Start

Define a microservices strategy for your system by partitioning the monolith into services with clear boundaries and applying event-driven communication and resilience patterns.

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 with clear boundaries?▼

Decompose a monolith by applying Domain-Driven Design to partition business capabilities into services with clear boundaries, per-service data ownership, and clear API contracts to ensure independent scalability and reliability.

When do I need the Saga pattern for distributed transactions?▼

You need the Saga pattern when managing distributed data across microservices with per-service data ownership, ensuring fault tolerance by coordinating transactions without relying on a global database commit.

How do circuit breakers improve microservices resilience?▼

Circuit breakers improve microservices resilience by preventing cascading failures during inter-service communication, isolating faults and stopping requests to struggling services to maintain overall system stability.

What is the best way to define inter-service communication in an event-driven architecture?▼

Define inter-service communication in an event-driven architecture by choosing between synchronous and asynchronous patterns, requiring clear API contracts to establish reliable integration and decouple service interactions.

Does this approach require per-service data ownership for microservices?▼

Yes, per-service data ownership is a strict requirement for this microservices approach, establishing clear service boundaries and decentralized data management to improve fault tolerance and scalability.

What are the limitations of service decomposition in distributed systems?▼

Service decomposition in distributed systems introduces complexity in inter-service communication and distributed data management, requiring resilience patterns like bulkhead isolation and retries to anticipate edge cases and manage constraints.