Microservices Fundamentals

Use When

• Core microservices concepts — monolith vs microservices trade-offs, decomposition patterns, the 12-Factor App adapted for microservices, bounded contexts, data isolation, and stateless design. Invoke before designing any microservices-based...
• The task needs reusable judgment, domain constraints, or a proven workflow rather than ad hoc advice.

Do Not Use When

• The task is unrelated to microservices-fundamentals or would be better handled by a more specific companion skill.
• The request only needs a trivial answer and none of this skill's constraints or references materially help.

Required Inputs

• Gather relevant project context, constraints, and the concrete problem to solve.
• Confirm the desired deliverable: design, code, review, migration plan, audit, or documentation.

Workflow