Skill

microservices-patterns

Applies microservices patterns for service boundaries, inter-service communication, data management, resilience, discovery, and event-driven architectures in distributed systems.

backend

devops

From antigravity-bundle-architecture-design

Install

Run in your terminal

npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-bundle-architecture-design

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

resources/implementation-playbook.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

cost-optimization

1 file

Optimizes cloud costs on AWS, Azure, GCP via rightsizing, tagging strategies, reserved instances, spot usage, and spending analysis. Use for expense reduction and governance.

cloud-infrastructure

33.0k

Stats

Parent Repo Stars30787

Parent Repo Forks5140

Last CommitMar 29, 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.