3 ms·
Except a Java container running a simple REST server is going to be a few hundred megs, while a similar Go container will be around 10 megs most likely. Which
by tsimionescu 4y ago
Except a Java container running a simple REST server is going to be a few hundred megs, while a similar Go container will be around 10 megs most likely.
Which doesn't matter all that much until you're distributing an app made out of 10-20 such services...
- pjmlp 4y agoSince Java 9 one can tier it down with jlink, previously the uberjar plugin could also be used for similar purposes.
- tsimionescu 4y agoThat's only true if your project and all your dependencies are modularized, right? I moved on to Go around the time Java 9 had recently come out, so no idea how well the ecosystem has evolved in this direction in the meantime. For the record, I miss many aspects of Java, especially the language and tooling, but Go was definitely the right choice for our project at the time. From what I've seen major Java projects are still delivered in large containers with a full JVM (ElasticSearch, Keycloak at least).
- pjmlp 4y agoNot with the uberjar approach. Many projects choose the easy way out when packing their deliveries, and to certain extent Java is having a Python 3 moment with anything past Java 8. The cynic in me sees that as the main reason why Docker was adopted, HP-UX was already having containers in 1999 and no one was rushing to package Perl into them.