Well, since you want to break up a monolith into microservices, it's like a rewrite. And if you're open to a rewrite, I thought of recommending a solid and mature framework like Spring. So I don't think it's bad advise, but my bad that I didn't add the detail about a rewrite.
If I were to do it, I would rewrite because it allows freedom to apply new design ideas when going down microservices route.
Well, now I have to say I find Spring quite a good framework based on personal experience. And the original poster asked for opinion, and I gave mine. Jeez so much analysis of my opinion? I'm flattered :-)
Please if ignore my replies if it is so wrong ....
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.
This is a bad piece of advice - it's advocating a complete rewrite from scratch. Is there a good reason to do this?
Well, since you want to break up a monolith into microservices, it's like a rewrite. And if you're open to a rewrite, I thought of recommending a solid and mature framework like Spring. So I don't think it's bad advise, but my bad that I didn't add the detail about a rewrite.
If I were to do it, I would rewrite because it allows freedom to apply new design ideas when going down microservices route.
Also your advocating a completely new language which is not exactly a great start without understanding the problem domian.
Well, now I have to say I find Spring quite a good framework based on personal experience. And the original poster asked for opinion, and I gave mine. Jeez so much analysis of my opinion? I'm flattered :-)
Please if ignore my replies if it is so wrong ....