First example, I can't tell how large the application is. "10 year old application (500k blocs of code)." 500k blocks of C++ code is very different with 500K blocks of python code. Not to mention if there are any deprecated codes that haven't been deleted. 5 people maintaining 500k blocks also make it harder to assume the size of the apps.
Second example, how many "feature" it has, and how it is dependent to each other. Because microservice and SOA usually separated per features/service. The more features it has, the more service that have to be developed, the more complex it will be. Especially if the features/services are dependent to each other. The decoupling will be very tricky to do.
Third example, how good and complex the datamodel is. the worse and the more complex the current datamodel, the more I'll go with microservice.
etc.
But the basic problem of developing the microservice is it will consume more resources: people, time, and money. So if the resources is pretty limited and the resource expansion is also limited, just go with SOA.
You need a capable consultant to answer this question anw. This kind of question won't get a proper answers in internet forums.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What's the missing informations you need ?
Many.
First example, I can't tell how large the application is. "10 year old application (500k blocs of code)." 500k blocks of C++ code is very different with 500K blocks of python code. Not to mention if there are any deprecated codes that haven't been deleted. 5 people maintaining 500k blocks also make it harder to assume the size of the apps.
Second example, how many "feature" it has, and how it is dependent to each other. Because microservice and SOA usually separated per features/service. The more features it has, the more service that have to be developed, the more complex it will be. Especially if the features/services are dependent to each other. The decoupling will be very tricky to do.
Third example, how good and complex the datamodel is. the worse and the more complex the current datamodel, the more I'll go with microservice.
etc.
But the basic problem of developing the microservice is it will consume more resources: people, time, and money. So if the resources is pretty limited and the resource expansion is also limited, just go with SOA.
You need a capable consultant to answer this question anw. This kind of question won't get a proper answers in internet forums.