Skill

microservices-patterns

Provides microservices architecture patterns for service boundaries, inter-service communication, data management, resilience, service discovery, and event-driven designs. Use for monolith decomposition and distributed systems.

backend

devops

npx claudepluginhub sickn33/antigravity-awesome-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

microservices-patterns

32.8k

1 file

antigravity-awesome-skills

microservices-patterns

682

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

1 file

rmyndharis-antigravity-skills

microservices-patterns

Provides microservices architecture patterns for service decomposition, communication, data management, resilience, and observability. Use for breaking down monoliths or designing distributed systems.

7 files

nickcrew-claude-ctx-plugin

Stats

Stars36383

Forks5961

Last CommitApr 13, 2026

Used By4 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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.

Limitations

Use this skill only when the task clearly matches the scope described above.

Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.