Quarkus Native or JVM Mode?
Вставка
- Опубліковано 6 лют 2025
- If you’ve seen Quarkus, you know that it gives you the possibility to compile your applications to native executables. But is that the best approach for most enterprise projects? In this video, I’m showing my perspective of what I think the most important features of Quarkus are, and whether we should favor the Quarkus native or JVM mode, in an enterprise project.
For more information see: blog.sebastian...
Quarkus on-demand video course: www.sebastian-...
Quarkus workshops in April: www.sebastian-...
Really amazing video explaining the difference between JVM mode and native mode in Quarkus. Thank you.
Makes so much sense 😊. Wow. JVM HotSpot outdoing c and other native languages in throughput - but watch out for RAM Usage spikes. I guess, it all depends on what you need 😂
Thank you!
Amazing video. Thanks
Nice video!
It would have been really cool if you had done a req/s comparison :(
Also, JVM almost 4 times more memory (OpenJDK), so even if JVM is faster, is it 4 times faster?
Because you could have 4 native images handling requests.
OpenJ9 is impressive though =D
Yes, the comparison for throughput per memory consumption (among other metrics) is also an interesting topic (though very nuanced because "it always depends" :)). Will add this to my list.
It always depends ❤
Using graalvm from docker fallback is very slow in macOS with M1. Better install graalVM in this case.
I tried mvn install -Pnative wasnt able to spin up a docker to build the native executable like yours
You might want to double-check your Docker runtime and whether you're using a matching Quarkus, Maven, and Java version. Also have a look here: quarkus.io/guides/building-native-image
Thanks for the very informative video. Unfortunately my work environment is still in the ages of Eclipse RCP and POJO applications :-/
Reduce the volume of the intro and boost the volume of your speech…. My ears bled
Thanks for pointing out, will do in the future