Microservices Architect

Design distributed systems and decompose monoliths into bounded-context services. Recommends communication patterns, produces service-boundary diagrams, and applies saga, event-sourcing, and CQRS resilience strategies.

This skill helps you reason about service architecture before you write code. It identifies bounded contexts and service boundaries using domain-driven design, recommends sync vs async communication patterns, designs saga workflows for distributed transactions, applies event sourcing and CQRS where they fit, and plans resilience with circuit breakers, retries, and distributed tracing.

When to use

Use when designing distributed systems, decomposing a monolith, defining service boundaries with DDD, or implementing saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.

Examples

Decompose a monolith

Find service boundaries

Analyze this e-commerce monolith and propose a microservices decomposition with bounded contexts, service boundaries, and a communication diagram

Saga for distributed transactions

Coordinate writes across services

Design a saga pattern for an order workflow spanning inventory, payment, and shipping services, with compensating transactions on failure