When the remaining monolith is maintainable and the split services cover the parts that needed independence. You do not need to split everything; some parts are fine in the monolith.
How Monoliths Evolve Into Microservices (Without a Big Rewrite)
When do I stop splitting a monolith?
The answer
More FAQs in How Monoliths Evolve Into Microservices (Without a Big Rewrite)
Use the strangler fig pattern. Pick a bounded context, extract it into a service with its own database, route traffic to it, and delete the old code from the monolith. Repeat.
Big-bang rewrites freeze the product for months and risk failure. The strangler fig pattern lets you ship each step independently and roll back if needed.
A feature with clear boundaries that can be extracted independently. Auth, payments, or notifications are good because they are self-contained. Pick something stable, not the part changing every week.
Still have questions?
Browse all our FAQs or reach out to our support team
Want to upskill yourself?
Your learning library
Small steps. Big possibilities.
Find your next course. Build something great.