Microservices (Deep Workflow)

Microservices trade code simplicity for operational and contract complexity. Justify each boundary with ownership and data isolation—not fashion.

When to Offer This Workflow

Trigger conditions:

• Splitting the monolith; coupling blocks independent deploys
• Latency cascades, partial failures, contract breaks
• Conway’s law alignment between teams and services

Initial offer:

Use six stages: (1) goals & constraints, (2) boundaries & data ownership, (3) integration patterns, (4) contracts & versioning, (5) reliability patterns, (6) ops & governance). Confirm org maturity and platform capabilities.

Stage 1: Goals & Constraints