Agent skill · product strategy · secondsky
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
Why this skill is useful
Provides specific patterns and executable code examples for designing microservices architectures that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 204 stars on the source repository.
What this skill does
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 from monolith New functionality as microservices Proxy routes to old/new systems 2. Communication Patterns Synchronous (Request/Response) REST APIs gRPC GraphQL Asynchronous (Events/Messages) Event streaming (Kafka) Message queues (RabbitMQ, SQS) Pub/Sub patterns 3. Data Management Database Per Service Each service owns its data No shared databases Loose coupling Saga Pattern Distributed transactions Compensating actions Eventual consistency 4. Resilience Patterns Circuit Breaker Fail fast on repeated errors Prevent cascade failures Retry with Backoff Transient fault handling Exponential backoff Bulkhead Isolate resources Limit impact of failures Service Decomposition Patterns Pattern 1: By Business Capability Pattern 2: API Gateway Communication Patterns Pattern 1: Synchronous REST Communication Pattern 2: Asynchronous Event-Driven Pattern 3: Saga Pattern (Distributed Transactions) Resilience Patterns Circuit Breaker Pattern Best Practices 1. Service Boundaries: Align with business capabilities 2. Database Per Service: No shared databases 3. API Contracts: Versioned, backward compatible 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills secondsky/microservices-patterns