microservices-architect
This skill guides architects through building cloud-native microservices systems from the ground up. It covers domain-driven service decomposition, communication pattern selection, data ownership strategies, resilience implementation, and observability setup—with concrete code examples for correlation IDs, circuit breakers, sagas, and Kubernetes probes.
Microservices Architect helps you design distributed system architectures and decompose monoliths into independently deployable services.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-05-20
Microservices Architect helps you design distributed system architectures and decompose monoliths into independently deployable services. This skill guides architects through building cloud-native microservices systems from the ground up. It covers domain-driven service decomposition, communication pattern selection, data ownership strategies, resilience implementation, and observability setup—with concrete code examples for correlation IDs, circuit breakers, sagas, and Kubernetes probes.
Use it when
- microservices-architect recommends applying domain-driven design to identify natural service boundaries before splitting.
- microservices-architect covers communication pattern selection based on your needs.
Verify before relying
Read SKILL.md below before installing (6 files). Open directory: indexed for reading, not audited.
Install
Jeffallan/claude-skills/microservices-architect · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I design a microservices architecture for a new distributed system?
microservices-architect guides you through building cloud-native systems by starting with domain-driven design to identify service boundaries and bounded contexts. Begin by mapping your business domain, then decompose it into loosely coupled services. Define clear APIs (REST or gRPC), establish data ownership with a database-per-service strategy, and plan your communication patterns—synchronous for tight coupling needs, asynchronous (Kafka, RabbitMQ) for eventual consistency. The skill provides concrete code examples for each phase.
What's the best way to decompose a monolith into microservices?
microservices-architect recommends applying domain-driven design to identify natural service boundaries before splitting. Map your domain's bounded contexts to candidate services, then refactor incrementally—extract one service at a time to minimize risk. Plan your database strategy (separate databases per service), choose communication patterns (REST, gRPC, or events), and implement resilience patterns like circuit breakers. The skill includes examples for correlation IDs, saga patterns for distributed transactions, and health probes for Kubernetes deployment.
How should microservices communicate—REST, gRPC, or messaging?
microservices-architect covers communication pattern selection based on your needs. Use synchronous REST or gRPC for request-response flows where you need immediate answers; choose asynchronous messaging (Kafka, RabbitMQ) for event-driven architectures and eventual consistency. Implement resilience strategies like circuit breakers, timeouts, and retries for all patterns. The skill provides implementation guidance for each, including correlation IDs for distributed tracing to track requests across services.
What resilience patterns should I implement for fault tolerance?
microservices-architect teaches key resilience patterns: circuit breakers prevent cascading failures, timeouts stop hanging requests, and retries with exponential backoff handle transient errors. For distributed transactions, use the saga pattern (orchestration or choreography). Implement distributed tracing with correlation IDs to track requests end-to-end. Add health checks and readiness probes in Kubernetes to detect and replace failing instances. Event sourcing and CQRS patterns support eventual consistency and audit trails.
How do I set up observability and monitoring for microservices?
microservices-architect guides distributed tracing, logging, and metrics collection across services. Use correlation IDs to link requests across service boundaries, enabling end-to-end visibility. Implement health checks and readiness probes for Kubernetes to monitor service health. Consider a service mesh (Istio) for advanced observability, traffic management, and fault injection. Combine logs, traces, and metrics to detect issues early and understand system behavior under load.
What deployment strategy works best for microservices?
microservices-architect recommends container orchestration (Kubernetes) with service mesh (Istio) for production deployments. Use health probes (liveness and readiness) to ensure only healthy instances receive traffic. Plan your API gateway strategy for external access and service mesh for internal communication, traffic management, and security policies. Implement gradual rollouts and canary deployments to minimize risk. Combine these with distributed tracing and observability to maintain system reliability.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Microservices Architect
Senior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence.
Core Workflow
- Domain Analysis — Apply DDD to identify bounded
(truncated - see the full file via the links below)
File tree — 6 files
skills/microservices-architect/SKILL.md
skills/microservices-architect/references/communication.md
skills/microservices-architect/references/data.md
skills/microservices-architect/references/decomposition.md
skills/microservices-architect/references/observability.md
skills/microservices-architect/references/patterns.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Design a microservices architecture for a new distributed system or decompose an existing monolith”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Expert guidance for architecting and operating microservices, from breaking down monoliths to managing inter-service communication and data consistency. Covers service boundaries, synchronous and asynchronous patterns, distributed transactions, circuit breakers, and observability strategies.
Learn to architect microservices by decomposing monoliths into independent services, managing inter-service communication through synchronous and asynchronous patterns, and implementing resilience strategies like circuit breakers and sagas. This skill covers service decomposition strategies, data management across distributed systems, and practical patterns for building fault-tolerant distributed architectures.
Get expert guidance on building scalable microservices systems with proven patterns like API Gateway, Circuit Breaker, and Saga for distributed transactions. Learn service discovery, asynchronous messaging, and failure-resilient design principles.
Master architectural patterns for building distributed systems through service decomposition, inter-service communication strategies, and fault tolerance techniques. Covers synchronous and asynchronous messaging, database ownership models, and resilience patterns like circuit breakers and bulkheads.
Make informed architecture decisions for new systems or major refactors. This skill guides you through pattern selection, scalability design, resilience strategies, and data consistency models—with concrete technology recommendations and tradeoff analysis. Covers decomposition, service boundaries, observability planning, and migration from legacy systems.
Master the decision to decompose systems into independent services and the patterns that keep them reliable. Covers bounded contexts, strangler fig extraction, synchronous vs. asynchronous communication, circuit breakers, saga patterns, and event sourcing—helping you avoid distributed monoliths and operational chaos.
More skills architecture-designer (MIT) · Java Microservices (NOASSERTION) · architecture-patterns (MIT) · microservices-architecture (MIT) · Microservices Patterns (unlicensed) · microservices-patterns (MIT) · event-driven-architecture (MIT) · golang-pro (MIT)