microservices-patterns
Master architectural patterns for building distributed systems through service decomposition, inter-service communication strategies, and fault tolerance techniques. Covers synchronous and asynchronous messaging, database ownership models, and resilience patterns like circuit breakers and bulkheads.
Microservices Patterns teaches you how to decompose monoliths into independently deployable services with clear boundaries.
AI-generated summary based on this skill's SKILL.md
Install
HermeticOrmus/LibreUIUX-Claude-Code/microservices-patterns · repository language: Shell
git clone https://github.com/HermeticOrmus/LibreUIUX-Claude-Code
cp -r LibreUIUX-Claude-Code/plugins/backend-development/skills/microservices-patterns ~/.claude/skills/microservices-patternsnpx skillfed install HermeticOrmus/LibreUIUX-Claude-Code/microservices-patternsFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I design microservices architecture?
microservices-patterns teaches you to design service boundaries by decomposing monoliths into independently deployable services. Start by identifying domain boundaries, define clear APIs between services, and establish ownership models. The skill covers synchronous (REST, gRPC) and asynchronous messaging approaches, helping you choose communication strategies that fit your system's consistency and latency requirements.
What are microservices service boundaries and decomposition?
microservices-patterns explains how to identify and establish service boundaries using domain-driven design principles. Learn decomposition strategies including the strangler fig pattern for migrating monoliths incrementally. The skill guides you through defining service responsibilities, managing dependencies, and implementing the database-per-service strategy to ensure true service independence and autonomous deployment.
How do I implement circuit breaker and resilience patterns?
microservices-patterns covers implementing resilience patterns essential for distributed systems. Learn circuit breaker pattern to prevent cascading failures, bulkhead pattern for resource isolation, and retry strategies with exponential backoff. These patterns protect your services from transient failures and help maintain system stability when downstream services experience issues or degradation.
How can I build event-driven asynchronous communication?
microservices-patterns teaches event-driven architecture using asynchronous messaging with tools like Kafka and RabbitMQ. Learn to decouple services through event publishing and subscription, implement eventual consistency models, and design event schemas. This approach reduces tight coupling between services and enables better scalability compared to synchronous request-response patterns.
How do I handle distributed transactions with saga pattern?
microservices-patterns explains the saga pattern for managing distributed transactions across multiple services. Learn orchestration and choreography approaches, implement compensation logic for rolling back failed steps, and handle eventual consistency. The skill covers how to coordinate long-running business processes while maintaining data consistency without traditional ACID transactions.
What's the role of API gateway and service discovery?
microservices-patterns covers API gateway patterns for routing client requests, handling cross-cutting concerns like authentication and rate limiting, and providing a unified entry point. Learn service discovery mechanisms for dynamic service registration and load balancing. These infrastructure components enable services to find each other and scale independently in distributed environments.
SKILL.md
rendered from the published skill — quoted content, verbatim
Microservices Patterns
Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.
When to Use This Skill
- Decomposing monoliths into microservices
- Designing service boundaries and contracts
- Implementing inter-service communication
- Managing distributed data and transactions
- Building resilient distributed systems
- Implementing service discovery and load balancing
- Designing event-driven architectures
Core Concepts
1. Service Decomposition Strategies
By Business Capability - Organize services around business functions - Each service owns its domain - Example: OrderService, PaymentService, InventoryService
By Subdomain (DDD) - Core domain, supporting subdomains - Bounded contexts map to services - Clear ownership and responsibility
Strangler Fig Pattern - Gradually extract
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
plugins/backend-development/skills/microservices-patterns/SKILL.md