Monolith Modularization (Deep Workflow)

Modularize before microservice splintering when possible: clear internal APIs and data boundaries lower risk than distributed rewrites.

When to Offer This Workflow

Trigger conditions:

• Tangled code; long build/test times; fear of changes
• Preparing for extract services later
• Team parallelism blocked by merge conflicts

Initial offer:

Use six stages: (1) map current state, (2) define target modules, (3) enforce boundaries, (4) migrate data & calls incrementally, (5) extract candidates, (6) validate & iterate. Confirm language ecosystem (Java modules, packages, etc.).

Stage 1: Map Current State