Skill

role-backend:microservices

Designs and implements microservices architectures including service decomposition, synchronous (REST/gRPC) and asynchronous (event-driven) communication, saga pattern, circuit breaker, service mesh (Istio), API gateway, service discovery, and distributed tracing. Use when decomposing monoliths, designing inter-service communication, or implementing resilience patterns.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin role-backend

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

- Evaluating whether microservices are the right architectural choice

Supporting Assets

references/decomposition-communication.mdreferences/resilience-infrastructure.md

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

role-backend:microservices

When to use

Evaluating whether microservices are the right architectural choice

Decomposing a monolith into independently deployable services

Designing inter-service communication (REST, gRPC, events, commands)

Implementing distributed transactions with the saga pattern

Adding circuit breakers, retries, or timeouts to outbound calls

Configuring service discovery, API gateway, or a service mesh

Setting up distributed tracing across service boundaries

Core principles

Services own their data — no shared databases; communicate through APIs or events

Design for failure — every remote call can and will fail; circuit breakers and retries are mandatory

Events are immutable facts — past tense names, schema-versioned from day one

Async by default — synchronous calls couple availability; use events where the caller does not need an immediate response

Operational complexity is the cost — microservices without tracing, health checks, and a deployment pipeline are just distributed monoliths

Reference Files

references/decomposition-communication.md — when to use (and not use) microservices, decomposition strategies (business capability, DDD bounded contexts, strangler fig), synchronous vs asynchronous communication patterns, and the saga pattern (choreography vs orchestration)

references/resilience-infrastructure.md — circuit breaker states and library options, API gateway responsibilities, service mesh trade-offs, service discovery approaches, distributed tracing with OpenTelemetry, retry/timeout strategy, and liveness/readiness health checks

Microservices

When to use

Evaluating whether microservices are the right architectural choice
Decomposing a monolith into independently deployable services
Designing inter-service communication (REST, gRPC, events, commands)
Implementing distributed transactions with the saga pattern
Adding circuit breakers, retries, or timeouts to outbound calls
Configuring service discovery, API gateway, or a service mesh
Setting up distributed tracing across service boundaries

Core principles

Services own their data — no shared databases; communicate through APIs or events
Design for failure — every remote call can and will fail; circuit breakers and retries are mandatory
Events are immutable facts — past tense names, schema-versioned from day one
Async by default — synchronous calls couple availability; use events where the caller does not need an immediate response
Operational complexity is the cost — microservices without tracing, health checks, and a deployment pipeline are just distributed monoliths

Reference Files

references/decomposition-communication.md — when to use (and not use) microservices, decomposition strategies (business capability, DDD bounded contexts, strangler fig), synchronous vs asynchronous communication patterns, and the saga pattern (choreography vs orchestration)
references/resilience-infrastructure.md — circuit breaker states and library options, API gateway responsibilities, service mesh trade-offs, service discovery approaches, distributed tracing with OpenTelemetry, retry/timeout strategy, and liveness/readiness health checks