I find that laughably generous. In my experience, Java gets a pass because it's "enterprise", whatever the hell that means. I've never heared anyone make a compelling case for Java on technical merit. It's always "we're a Java shop, because we're enterprise".
Re:Debunking the Java Performance Myth
by RhodesianHunter on Sunday October 22, 2017 @11:12AM
(#15527140)
"I've never heared anyone make a compelling case for Java on technical merit."
IMO this is a sign that you should expand the company you keep rather than being indicative of any flaw with Java.
Because you can find libraries for all the "Enterprise" technologies easily. Besides .net, not many ecosystems offer that kind of library support. From XML signatures, to pkcs11, to complete soap support (including ws-security), to many others.
Fact is, in the Enterprise you'll have to interface with many of the aforementioned technologies, and Java still has the most support for them. We find that even in .net we sometimes have to implement some things on our own from the horribly convoluted "Enterprise" technologies because a specific feature isn't supported.
If you're a business making a language choice based on the technical merits of the language itself, you are very much doing it wrong.
You say there is no technical merit to use Java ecosystem over something else?
Even if some requests needs crunchy CPU power, it's better to offload them into something asynchronous than try really hard to make them perform well enough to be synchronous. Typically, hefty CPU jobs come in varying sizes, they're rarely guaranteed to be runnable under the 200ms or so latency bar for synchronous requests.