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
El comando exacto puede variar según el repositorio. Consulta el README en GitHub.
Para el autor de la skill
Pega en el README de tu repo
Muestra que tu skill está catalogada en Skillteca, genera backlink y tráfico rastreable.
[](https://www.skillteca.com.br/skills/microservices-architect-keez97?utm_source=badge&utm_medium=readme&utm_campaign=badge)
Recibe nuevas skills de Design e Frontend todos los lunes
Un email corto con solo las skills nuevas de Design e Frontend. 4 minutos de lectura, sin spam, te das de baja con un clic.
Confirmas tu email en el primer envío. Sin spam. Te das de baja con un clic.
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.]