Design microservices architectures with service boundaries
Microservices patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
--- 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. --- # 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
Overview
Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.
Manual install (npx, ZIP)
Claude Code
npx skills add wshobson/agents --skill microservices-patterns -g -a claude-codeClaude Code (manual)
mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/wshobson/agents/tar.gz/4236bb91f839 \
| tar -xz -C ~/.claude/skills --strip-components=4 agents-4236bb91f839/plugins/backend-development/skills/microservices-patternsWindows (PowerShell)
New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/ed07911ec6cea18ea54c/microservices-patterns.zip" -OutFile "$env:TEMP\microservices-patterns.zip"; Expand-Archive "$env:TEMP\microservices-patterns.zip" -DestinationPath "$HOME\.claude\skills" -ForceClaude.ai / desktop
Codex, Cursor, other agents
Connects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md2.1 KBreferences/1 file · 14.1 KB
Read the files here
SKILL.md
Show the full text91 lines
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
Detailed patterns and worked examples
Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.
| 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 | |
| 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 |
Details
- Updated
- Sep 21, 2026
- License
- MIT
- Stars on the repo
- ★ 39,857
- Checked
- Source
- wshobson/agents ↗
- Creator
- wshobson · 179 listings
Similar skills
See all →
SkillA task is too large for one model passAdvisor orchestrator worker
Shubhamsaboo/awesome-llm-apps · by ShubhamsabooUse when a task is too large for one model pass, needs parallel research or generation across many subtasks (like researching a dozen competitors at once), or the user asks to orchestrate multiple models, split work across a model team, run an advisor-worker loop, have a stronger model review the plan while cheap workers execute, or says "too big for one model" or "fan this out". Not for single-file edits or tasks one model handles in one pass.★ 139k GitHub stars
SkillRun the CCS Align seat's hourly breathing cycleCCS Align — Worker Watch seat (Phases 0–2 shipped; Phase 3 = verify / sign-off)
thedotmack/claude-mem · by thedotmackRun the CCS Align seat's hourly breathing cycle — prove the local claude-mem worker is healthy, pull needle observations through search → timeline → get_observations, land them in a seat-owned middle cache via atomic grab → append → filter exclude-marks → replace, manage exclude marks, and walk house → project → seat rules to detect conflicts (SHADOW_HOUSE, DENY_ALLOW, DRIFT, CLOCK_HEADER) with an append-only rules-report.md. Use when asked to run CCS Align, breathe the alignment seat, refresh the middle cache, exclude or restore an observation, walk rules, check rules conflicts, or check the Worker Watch board.★ 95.6k GitHub stars
SkillSummarize and review what changed while you were awayCatchup — Async-Team Return Briefing
oliver-kriska/claude-elixir-phoenix · by oliver-kriskaSummarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.★ 560 GitHub stars
SkillMaster Python asyncio, concurrent programmingAsync python patterns
wshobson/agents · by wshobsonMaster Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.★ 39.9k GitHub stars
SkillMaster Go concurrency with goroutines, channelsGo concurrency patternswshobson/agents · by wshobsonMaster Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.★ 39.9k GitHub stars
SkillMaster ES6+ features including async/await, destructuringModern javascript patternswshobson/agents · by wshobsonMaster ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, efficient JavaScript code. Use when refactoring legacy code, implementing modern patterns, or optimizing JavaScript applications.★ 39.9k GitHub starsMore from wshobson
SkillMaster C/.NET backend development patterns for buildingwshobson/agents · by wshobsonMaster C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.★ 39.9k GitHub stars
SkillImplement WCAG 2.2 compliant interfaces with mobileAccessibility compliancewshobson/agents · by wshobsonImplement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.★ 39.9k GitHub stars
SkillMaster Material Design 3 and Jetpack Compose patternsAndroid Mobile Designwshobson/agents · by wshobsonMaster Material Design 3 and Jetpack Compose patterns for building native Android apps. Use when designing Android interfaces, implementing Compose UI, or following Google's Material Design guidelines.★ 39.9k GitHub stars
SkillMigrate from AngularJS to Angular using hybrid modeAngular migrationwshobson/agents · by wshobsonMigrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code.★ 39.9k GitHub stars
SkillUnderstand anti-reversing, obfuscationAnti reversing techniqueswshobson/agents · by wshobsonUnderstand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use this skill when analyzing malware evasion techniques, when implementing anti-debugging protections for CTF challenges, when reverse engineering packed binaries, or when building security research tools that need to detect virtualized environments.★ 39.9k GitHub stars
SkillBuild production Apache Airflow DAGs with best practicesApache Airflow DAG Patternswshobson/agents · by wshobsonBuild production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.★ 39.9k GitHub stars