I don't fully agree with a lot of concerns others posted here, the simple reality is this, micro-service architecture is great if you know how to do it and horrible if you don't. Be honest with yourself do you really know what problems you will encounter and will you know how to deal with those problems? I would suggest not to do micro service architecture unless you've read a comprehensive book on it e.g. Microservice Patterns because the changes are you don't know what you are getting yourself into.
I don't fully agree with a lot of concerns others posted here, the simple reality is this, micro-service architecture is great if you know how to do it and horrible if you don't. Be honest with yourself do you really know what problems you will encounter and will you know how to deal with those problems? I would suggest not to do micro service architecture unless you've read a comprehensive book on it e.g. Microservice Patterns because the changes are you don't know what you are getting yourself into.
To be able to refactor a large legacy code base I would recommend looking into Vertical Slice Architecture and before you fall into the trap of unit tests watch this talk TDD, Where Did It All Go Wrong