Skip to content
Back to skills

Microservices Patterns

ASecurity

Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

  • 31 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 6, 2026
ai-agentsrails

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add frank-luongt/faos-skills-marketplace --skill microservices-patterns --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Microservices Patterns?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Microservices Patterns
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/frank-luongt-microservices-patterns/badge)](https://www.skillsdirectory.com/skills/frank-luongt-microservices-patterns)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
<!-- AUTO-GENERATED by export-plugins.py — DO NOT EDIT -->
---
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.
tags: [architecture, microservices]
---

# Microservices Patterns

Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

## Use this skill when

- 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

## Do not use this skill when

- The system is small enough for a modular monolith
- You need a quick prototype without distributed complexity
- There is no operational support for distributed systems

## Instructions

1. Identify domain boundaries and ownership for each service.
2. Define contracts, data ownership, and communication patterns.
3. Plan resilience, observability, and deployment strategy.
4. Provide migration steps and operational guardrails.

## Resources


<!-- Source: .faos/custom/skills/architecture/microservices-patterns/SKILL.md -->

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…