Recently I wrote a service using embedded tomcat libraries. It contains few lines of code to boot up tomcat, add servlets, set some context parameters. There are no configuration files, no annotations or a readymade stack of libs that I must use. Now it works fine but no hope of going in production because it does not use the next generation state of the art Spring boot microservices framework as recommended by architecture group.
I guess point here is unless code is smothered with multiple layers of frameworks companies will not like it.
> because it does not use the next generation state of the art Spring boot microservices framework as recommended by architecture group.
Well... how closely are they looking? Not even joking here, although it's kind of funny in a sad way. I've had clueless "enterprise architecture" groups demand that I use some pointless framework or other - some EAI or ESB or ORM or something else that 100% gets in the way and 0% enhances productivity. So what I do is, I declare a dependency on the framework, use just enough of it so they can't say I'm _not_ using it, and then go ahead and write the damned code so that it works and avoids the pointless "framework" they're cramming down my throat.
FWIW this is just the way life is in large companies: you have to trade-off individuality vs. company-wide productivity.
Granted, both extremes are bad, and finding a happy medium is hard.
Hopefully the architecture group's "recommended"/mandated stack also includes great out-of-the-box, company-wide tooling like metrics, error logging, etc., etc.
If their solution doesn't provide these perks, well, yes, that's not as useful.
> Hopefully the architecture group's "recommended"/mandated stack also includes great out-of-the-box, company-wide tooling like metrics, error logging, etc., etc.
Mostly they jump on hype train. Few months back it was netflix stack now it seems they are moving to something else. My main work is on a large(ish) application which is in production long before merger. So for now I am not forced on to jump on their architectural astronautery. I just play around with other technologies etc.
Then you should be able to rewrite that into a spring boot application in a day at most and the company gets the advantage of a more homogeneous software stack that can be more easily be extended with metrics or whatever.
It contains few lines of code to boot up tomcat, add servlets, set some context parameters.
I've done this with Jetty, and sure the first few handlers/servlets are dead simple. But when it starts to grow, manually coding these things becomes unruly quickly. As the other commentor says, converting this to Spring Boot should be easy, and a good learning exercise.
IMO Springs killer feature is the AOP transaction manager. It lets the dev team forget about it completely and only focus on transaction details for corner cases when the default rollback on exceptions mechanism is not desired.
I guess point here is unless code is smothered with multiple layers of frameworks companies will not like it.