arch-microservices
Installation
SKILL.md
One-line summary
Decompose the system into independently deployable services, each owning its data and aligned with a business capability. Communicate over the network. Pay the operational tax in exchange for autonomy and independent scaling.
When to use this skill
- Multiple teams stepping on each other in a single codebase / deployment.
- Different parts of the system need independent scaling characteristics (one is CPU-bound, another I/O-bound, a third bursty).
- Different parts have different release cadences and one team's deploy must not block another's.
- Different parts have different reliability profiles (a critical payment path; a non-critical analytics dashboard).
When NOT to use this skill
- One team, one product, no scaling pressure — you don't have the problems microservices solve. Keep the monolith.
- Domain not understood well enough to draw service boundaries — premature splits are very expensive to reverse.
- No operational maturity (no CI/CD, no observability, no on-call) — microservices amplify operational pain.
- Resume-driven development. Stop.