3 ms·
> because it does not use the next generation state of the art Spring boot microservices framework as recommended by architecture group. Well... how closely ar
by commandlinefan 9y ago
> 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.