Microservices Patterns
Unverified●30/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add microservices-patternsWho is stuck, and on what
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
The whole source
Frontmatter — 2 properties
| name | microservices-patterns |
|---|---|
| description | Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices. |
| 1 | --- |
| 2 | name: microservices-patterns |
| 3 | description: Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices. |
| 4 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 5 | |
| 6 | # Microservices Patterns |
| 7 | |
| 8 | Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems. |
| 9 | |
| 10 | ## When to Use This Skill |
| 11 | |
| 12 | - Decomposing monoliths into microservices |
| 13 | - Designing service boundaries and contracts |
| 14 | - Implementing inter-service communication |
| 15 | - Managing distributed data and transactions |
| 16 | - Building resilient distributed systems |
| 17 | - Implementing service discovery and load balancing |
| 18 | - Designing event-driven architectures |
| 19 | |
| 20 | ## Core Concepts |
| 21 | |
| 22 | ### 1. Service Decomposition Strategies |
| 23 | |
| 24 | **By Business Capability** |
| 25 | |
| 26 | - Organize services around business functions |
| 27 | - Each service owns its domain |
| 28 | - Example: OrderService, PaymentService, InventoryService |
| 29 | |
| 30 | **By Subdomain (DDD)** |
| 31 | |
| 32 | - Core domain, supporting subdomains |
| 33 | - Bounded contexts map to services |
| 34 | - Clear ownership and responsibility |
| 35 | |
| 36 | **Strangler Fig Pattern** |
| 37 | |
| 38 | - Gradually extract from monolith |
| 39 | - New functionality as microservices |
| 40 | - Proxy routes to old/new systems |
| 41 | |
| 42 | ### 2. Communication Patterns |
| 43 | |
| 44 | **Synchronous (Request/Response)** |
| 45 | |
| 46 | - REST APIs |
| 47 | - gRPC |
| 48 | - GraphQL |
| 49 | |
| 50 | **Asynchronous (Events/Messages)** |
| 51 | |
| 52 | - Event streaming (Kafka) |
| 53 | - Message queues (RabbitMQ, SQS) |
| 54 | - Pub/Sub patterns |
| 55 | |
| 56 | ### 3. Data Management |
| 57 | |
| 58 | **Database Per Service** |
| 59 | |
| 60 | - Each service owns its data |
| 61 | - No shared databases |
| 62 | - Loose coupling |
| 63 | |
| 64 | **Saga Pattern** |
| 65 | |
| 66 | - Distributed transactions |
| 67 | - Compensating actions |
| 68 | - Eventual consistency |
| 69 | |
| 70 | ### 4. Resilience Patterns |
| 71 | |
| 72 | **Circuit Breaker** |
| 73 | |
| 74 | - Fail fast on repeated errors |
| 75 | - Prevent cascade failures |
| 76 | |
| 77 | **Retry with Backoff** |
| 78 | |
| 79 | - Transient fault handling |
| 80 | - Exponential backoff |
| 81 | |
| 82 | **Bulkhead** |
| 83 | |
| 84 | - Isolate resources |
| 85 | - Limit impact of failures |
| 86 | |
| 87 | ## Detailed patterns and worked examples |
| 88 | |
| 89 | Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. |
| 90 | |
| 91 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current session◐◐◐◐◐●36/40Python Code Style & DocumentationPython code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.◐····●35/40Competitor Price Analysis 💲Competitor pricing strategy analysis and market positioning. Price mapping, pricing gaps identification, elasticity signals evaluation, and strategic pricing optimization. Use when the user asks about competitor pricing, price analysis, pricing strategy, or co◐····●34/40Competitor Price Tracker 📊Set up competitor price tracking and monitoring workflows. Track price changes, detect promotions, analyze pricing patterns, and get alerts for competitive price movements.◐····●34/40