Microservices Architect
技能 已验证 活跃Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.
To provide expert guidance and structured workflows for designing, decomposing, and implementing robust microservices architectures.
功能
- Designs distributed system architectures
- Decomposes monoliths into bounded-context services
- Recommends communication patterns (sync/async)
- Produces service boundary diagrams and resilience strategies
- Covers DDD, event sourcing, CQRS, service mesh, and distributed tracing
使用场景
- Designing new distributed systems from scratch
- Decomposing existing monolithic applications into microservices
- Implementing microservices patterns like DDD, sagas, and CQRS
- Choosing appropriate communication protocols and resilience strategies
非目标
- Writing actual code for services
- Configuring deployment pipelines directly
- Managing infrastructure for microservices
- Providing specific framework implementations beyond illustrative examples
实践
- Domain-Driven Design
- API Design
- Resilience Patterns
- Asynchronous Communication
- Event-Driven Architecture
安装
请先添加 Marketplace
/plugin marketplace add jeffallan/claude-skills/plugin install claude-skills@fullstack-dev-skills质量评分
已验证类似扩展
Microservices Patterns
98Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
V3 Ddd Architecture
100Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
Backend Api Design
99Design RPC-style APIs with layered architecture (Controller → Manager → Repository). Use when creating new API endpoints, designing API contracts, or reviewing API patterns.
System Design
99Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.
Workflow Orchestration Patterns
99Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
Instrument Distributed Tracing
99Instrument applications with OpenTelemetry for distributed tracing, including auto and manual instrumentation, context propagation, sampling strategies, and integration with Jaeger or Tempo. Use when debugging latency issues in distributed systems, understanding request flow across microservices, correlating traces with logs and metrics for root cause analysis, measuring end-to-end latency, or migrating from legacy tracing systems to OpenTelemetry.