Uh at the very least Java is bad. the java programs we run take 4 gigs and burn my entire compute. Every1 used spring or guice and the di runtime, so tests are expensive for e2e with mocks. There’s no scrutable way I can run more than 2 or 3 on a standard laptop without burning out the thing.

Go can.

That could be a Spring issue then, not Java. Do you run with -Xmx specified?

Yes, but different services varied.

I think we experimented between 4096 and 8192 to measure p99 latency performance and that was the optimal as tradeoff.

You don't have to use Spring or the typical enterprise IOC that plagued 00s and 10s Java.

I mean yes true but no one would justify migrating the code it’d be so expensive.

Dagger was very nice for the newer services and the ones that used straight rx were like less hell

You might want to check out Quarkus, Mirconaut, or Helidon MP. They do build time DI, and are more focused on performance and reduced resource usage. They are similar enough to Spring, and I believe Quarkus and Micronaut have an optional Spring compatibility layer that one can use. LLMs could help with migration if the codebase is well written.

You might also want to checkout Project Leyden[1]

https://openjdk.org/projects/leyden/