Receber por email
← Voltar para o catálogo

microservices-architect

Design distributed systems using microservices patterns. Triggers on: microservices, service mesh, distributed systems, event-driven architecture, saga pattern, service boundaries, monolith to microservices, API gateway, message queue, eventual consistency, circuit breaker, gRPC, service decomposition. Provides ADRs, service boundary diagrams, API contracts, data flow analysis, and failure mode as

2estrelas
Atualizado há 5 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add keez97/claude-architecture-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/microservices-architect-keez97/svg)](https://www.skillteca.com.br/skills/microservices-architect-keez97)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Microservices Architecture Skill

Core Philosophy

Distributed systems introduce complexity that's not worth paying unless you genuinely need it. Most teams reach for microservices too early. Start with a modular monolith. Add microservices only when:

  • You have independent scaling needs per domain
  • You need true deployment independence
  • Your team is large enough to own separate services
  • Your data access patterns don't require tight consistency

The monolith-first argument: A well-s

[Description truncada. Veja o README completo no GitHub.]

Compartilhar X LinkedIn