microservices-patterns
Skill0 starsChanged 47 days agoMITView on GitHub
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
18 other projects use a version of this, 12 of them edited.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillsedited, first seen Nov 16, 2026
- svngoku/coding-agents-skillstheir own version, first seen Nov 1, 2026
- xfstudio/skillsedited, first seen Oct 13, 2026
- Samueladewole/claude-skillsedited, first seen Oct 13, 2026
- Ghosteken/agent-harnessedited, first seen Oct 1, 2026
- roshankodi/agent-skillsword for word, first seen Sep 22, 2026
Used with
Projects with it also use attack-tree-construction, sql-optimization-patterns and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
xfstudioSkillattack-tree-construction
Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.
Also in 3 projects that use this
AJBcodingSkillsql-optimization-patterns
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
Also in 5 projects that use this
xfstudioSkillerror-handling-patterns
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
Also in 5 projects that use this
GSA-TTSSkillarchitecture-decision-records
Load when a user wants architecture decision records (ADRs) drafted from requirements or a design discussion, asks which decisions need an ADR, or wants an ADR draft reviewed for one-sided trade-offs, weak alternatives or missing requirement links. Not for setting up a project's whole documentation system (project-documentation-system).
Also in 6 projects that use this
AJBcodingSkillpython-performance-optimization
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.
Also in 3 projects that use this
HABUBUSSSkillbackend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
Also in 3 projects that use this
- +4 more from xfstudio
Other versions18 projects use a version of this.
Word for word · 1
- roshankodi/agent-skills★ 2100% same
Edited · 12
- nilecui/SkillsBase★ 2712% same
- xfstudio/skills★ 947% same
- HK-hub/AgentSkills★ 612% same
- GPTtang/skill-atlas★ 412% same
- ai4brands-design/claude-skills★ 247% same
- CodeWithBehnam/cc-docs★ 213% same
- Ghosteken/agent-harness★ 225% same
- NorkzYT/claude-code-autopilot★ 212% same
- AtilaMedeiros/skills★ 147% same
- iCesofT/awesome-ai★ 141% same
2 more not listed
Wrote their own version · 5
- tranhieutt/software_development_department★ 71same name
- svngoku/coding-agents-skills★ 12same name
- wpank/ai★ 11same name
- mmondora/claude-skills★ 1same name
- dhriyatinandu-bot/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- async-python-patternsSkill
- bun-runtimeSkill
- contract-firstSkill
- distributed-tracingSkill
- docker-patternsSkill
- fastapi-patternsSkill
- golang-concurrencySkill
- golang-error-handlingSkill
- golang-grpcSkill
- golang-patternsSkill
- golang-performanceSkill
- golang-testingSkill
- grpc-microservices-guardSkill
- openapi-spec-generationSkill
- redis-patternsSkill
- social-media-automation-orchestratorSkill
- tdd-workflowSkill
- verification-loopSkill
- x-apiSkill
- grpc-microservices-guardSkill
- tiktok-growth-automation-meshSkill
- social-media-automation-orchestratorSkill
The file
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

