architecture-paradigm-microservices

Decompose systems into a suite of small, independently deployable services alignedto specific business capabilities.Triggers: microservices, service decomposition, independent deployment, team autonomy,distributed system, API gateway, service mesh, bounded contexts, polyglot persistenceUse when: teams need high autonomy and independent releases, different capabilitieshave distinct scaling needs, strong DevOps/SRE maturity exists, polyglot tech stacks neededDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: small team with low organizational complexity.DO NOT use when: lack of DevOps maturity or limited platform engineering resources.DO NOT use when: strong transactional consistency required across operations.Consult this skill when designing or evolving microservices architectures.