Hacker News new | ask | show | jobs
by RedlineTriad 1100 days ago
I tried the Quarkus version, but it does some kind of build step at container startup, and that is what used the most memory.

You can apparently build an "optimized" image[1] so it doesn't do it at runtime, but I didn't want to build a custom image, and I felt like the KeyCloak philosophy didn't align with my own.

In general I found myself avoiding Java applications because of their memory footprint.

[1] https://www.keycloak.org/server/containers#_creating_a_custo...

1 comments

I understand your reluctance to use Java, but it's actually pretty good if the developers use small libraries instead of the giant frameworks most Java servers use... a Java server for this kind of stuff will run within 200MB+ comfortably and with very high performance when written properly. Anything using 3GB for this stuff is doing something terribly wrong.
Yeah I know, nothing except maybe the JIT that requires java programs to use more memory than Go, but in practice Java apps are almost always significantly worse. C# is also pretty bad, but not quite as bad I think.

I can only assume it's a cultural thing since reflection and abstraction is used so much.

Rust apps are always nice since they are generally <20MB or something.