←back to thread

One year after switching from Java to Go

(glasskube.dev)
257 points pmig | 1 comments | 18 Feb 25 16:55 UTC | HN request time: 1.189s | source
Show context
pseudoramble ◴[18 Feb 25 22:58 UTC] No.43096211[source]▶
I’ve been out of the Java scene for a really long time, but will be coming back to it soon. I’m curious - these performance issues described here, are they inherit to how Java itself? Is it baggage from Spring/Boot? Are there ways to get more bang for the buck with some careful choices in a system like this?

The closest I’ve done to Java recently is C#, which I think may have similar challenges, but overall didn’t seem quite as bad if you avoided lots of framework extras. It also wasn’t something I was digging into deeply though, so perhaps I’m mistaken.

replies(6): >>43096295 #>>43096314 #>>43096318 #>>43096420 #>>43096427 #>>43100389 #
gred ◴[18 Feb 25 23:09 UTC] No.43096318[source]▶
My experience with very simple Jersey web apps is ~1.5 seconds to start up. Much less than his reported ~8 seconds with Spring Boot, but still not in the 100 ms range he reports with Go. I assume one second or so is about as low as you can go with a mainstream Java framework without AOT, though I'd be happy to be corrected.
replies(3): >>43096340 #>>43096666 #>>43100143 #
1. matsemann ◴[19 Feb 25 09:06 UTC] No.43100143[source]▶
Also, you don't have to continuously restart the server for every change. Can hot swap code. And for tests there are solutions to keep the jvm running between the code->test->fix cycle. But I've never felt the need for those, running a single test is often plenty fast as one doesn't need to instantiate the whole app, only the dependencies needed for the test. So plenty fast.