Skill

microservices-patterns

Designs microservices architectures with service boundaries, event-driven communication, data management, and resilience patterns. Use for decomposing monoliths or building distributed systems.

backend

devops

Install

npx claudepluginhub joshuarweaver/cascade-code-general-misc-2 --plugin rmyndharis-antigravity-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

Supporting Assets

resources/implementation-playbook.md

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Stars682

Forks124

Last CommitJan 18, 2026

Actions

View Source View Plugin View on GitHub View README

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

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

Resources

resources/implementation-playbook.md for detailed patterns and examples.