News for hackers. Stuff that matters.

A comment on Uber Engineering Tricks of the Trade: Tuning JVM Memory for Large-Scale Services. Parent comment

Re:Uber Engineering Tricks of the Trade: Tuning JVM Memory f... by viscanti on Tuesday May 18, 2021 @04:08PM (#27200337)
> I am surprised how much legacy inefficient crap is lingering around in companies like Uber.

Maybe there are some JVM specific libraries they need for things like mapping that don't exist on GoLang? From reading their tech blog, it sounds like they're mostly a GoLang shop and they were apparently Python before that. So it seems like they're probably forced into using Java because some of the libraries they use aren't worth rewriting in-house to avoid having to use the JVM.

[ Parent | on HN ]
Re:Uber Engineering Tricks of the Trade: Tuning JVM Memory f... by StreamBright on Tuesday May 18, 2021 @05:04PM (#27201117)
Don’t get me wrong I have nothing against Java/JVM. I pretty much appreciate that tech. The criticism was specifically against Hadoop. I spent nearly 10 years on it. Luckily it is stack that most companies migrating away from.
[ Parent | on HN ]
Re:Uber Engineering Tricks of the Trade: Tuning JVM Memory f... by gher-shyu3i on Tuesday May 18, 2021 @05:17PM (#27201275)
What do they migrate to if they need on-prem solutions?
[ Parent | on HN ]