What characteristics define "legacy hell"?
I'm curious, and the specific list of problems and pain points (if--big if!--everyone there agrees what they are) can help more clearly guide the decisions as to what the next architecture should look like--SoA, monolithic, and so on.
Say more? That sounds like an old codebase, and poor programming practices. What about the codebase and your struggles with it suggests that a rearchitecture is in order? What about it suggests that microservices might be the right solution?
I apologize if that sounds critical; it's not meant to be. Microservices/SoA are often the best available solution given human and technical constraints--I'm not skeptical, just curious.
I never said microservices were a solution, I said a service-oriented architecture is a giant leap forwards for a legacy platform.
This whole thread is about how microservices are often abused when they're not necessary, and to clarify my point, I completely agree with that.
Try 20+ year of git history. (yes they migrated to git from svn).
The biggest obstacle is changing people's mindsets from legacy programming to modern DevOps workflow. Making them believe it's worth the effort.