Java JIT vs. Java AOT vs. Go for Small, Short-Lived Processes

Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce... by evacchi on Tuesday December 24, 2019 @10:09AM (#21872499)

it's not "free", but there are frameworks that may help with that; e.g. Quarkus [1] provides a common EE/MicroProfile stack that does a lot of AoT codegen to get faster boot times and lower memory footprint; it is also compatible with GraalVM AoT, for even lower footprint and faster bootup. Compile times are still large, but you get the benefit of a familiar stack. Notice that, however, if your workload is throughput-intensive, you may still want to go with JVM mode (which is still pretty fast because of codegen)

(full disclosure: I work at Red Hat and I have contributed to the project)

[1] https://quarkus.io/

[ Parent | on HN ]

Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce... by vips7L on Tuesday December 24, 2019 @11:18AM (#21872990)

I've written a small project in Quarkus and I have enjoyed it. My main problems are the windows support still isn't there yet and the support for graal 19.3 (the one that supports java 11) isn't done yet either.

[ Parent | on HN ]