From a modular monolith to microservices without a rewrite

Most “monolith to microservices” stories go one of two ways. Either it’s a rewrite that takes eighteen months and ships a system nobody asked for, or it’s a big-bang split into fifteen services that immediately need a Kubernetes team. Both come from the same mistake: treating “process boundaries” and “module boundaries” as the same decision.