Microservices Patterns
- 196 repo stars
- Updated July 25, 2026
- secondsky/claude-skills
Design microservices architectures with clear service boundaries, event-driven communication, and resilience patterns when decomposing monoliths.
About
A skill for designing microservices architectures with well-defined service boundaries, event-driven communication, and resilience patterns. Developers use it when constructing distributed systems, decomposing monoliths, or implementing microservices from scratch.
- Service boundaries
- Event-driven communication
- Resilience patterns
- Monolith decomposition
Microservices Patterns by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin marketplace add secondsky/claude-skills/plugin install microservices-patterns@claude-skillsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 196 |
|---|---|
| Last updated | July 25, 2026 |
| Repository | secondsky/claude-skills ↗ |
What it does
Design microservices architectures with clear service boundaries, event-driven communication, and resilience patterns when decomposing monoliths.
README.md
Microservices Patterns Skill
Design distributed systems with service boundaries, event-driven communication, and resilience patterns.
Overview
This skill provides comprehensive guidance on microservices architecture including service decomposition, inter-service communication, data management, and resilience patterns for building reliable distributed systems.
When to Use
- 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 Patterns
Service Decomposition
- By business capability
- By subdomain (DDD)
- Strangler Fig pattern for gradual migration
- API Gateway for aggregation
Communication
- Synchronous: REST, gRPC, GraphQL
- Asynchronous: Event streaming (Kafka), Message queues (RabbitMQ, SQS)
- Request/Response vs Event-Driven
Data Management
- Database per service (no shared databases)
- Saga pattern for distributed transactions
- Eventual consistency
- Compensating actions
Resilience
- Circuit Breaker pattern
- Retry with exponential backoff
- Bulkhead isolation
- Health checks and service discovery
Auto-Trigger Keywords
- microservices architecture
- service decomposition
- distributed systems
- event driven architecture
- saga pattern
- circuit breaker
- API gateway
- service mesh
- inter-service communication
- database per service
- eventual consistency
Source
Adapted from wshobson/agents
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.471k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.382k15.8kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.381k15.8k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k37Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.230k15.8k
SupabaseGet accurate, up-to-date Supabase implementation guidance across database, auth, realtime, storage, edge functions and vector search without relying on outd182k2.4k