[bcaxis]

You could solve this other ways. Build a new better monolith and have a reverse proxy route between them and slowly update and move routes over. You will get through a rewrite slowly one bit at a time.

If you keep the same database schema this should generally work pretty well.

I migrated a terribly written web app this way, it worked pretty well.

[sjducb]

The application was written by a team of 20 over 10 years. There are over 3000 database tables.

The job it does is big and complicated. It is used by teams all over the world.

The problem is the inherent complexity of the business domain. Not poor quality code from devs 10 years ago.

[bcaxis]

Apparently I don't understand. If the code isn't poor, why throw it away for a new even more complex system? I don't know how code isn't poor, yet is indecipherable.

Regardless, the method works even in a complex environment.