Extract three services, leave the monolith alone
Full decomposition is a multi-year programme that usually stalls halfway, leaving two architectures to operate. Extracting the components that actually hurt is a quarter and it finishes.
Anita Deshmukh, Chief Technology Officer ·
Which components actually fail
Load and incident history usually point at a small number of components. Those are the extraction candidates. The rest of the monolith is typically fine, and rewriting it buys nothing but risk.
Facades, so nothing else changes
Put the extracted service behind the interface the monolith already calls. The rest of the system does not learn that anything moved, and the extraction can be reversed if it goes badly.
Stop when it stops hurting
The goal is a system that survives peak, not a diagram with no monolith on it. Declare the programme finished when the pain is gone, and resist the tidiness argument for continuing.