Quarkus Native or JVM Mode?

[@harshpamnani8530]

Really amazing video explaining the difference between JVM mode and native mode in Quarkus. Thank you.

[@RafaelDurelli]

Amazing video. Thanks

[@josemdiaza]

Thank you!

[@abrahammoyo3457]

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 😂

[@LeandroCoutinho]

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

[@SebastianDaschnerIT]

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.

[@abrahammoyo3457]

It always depends ❤

[@jkho8365]

I tried mvn install -Pnative wasnt able to spin up a docker to build the native executable like yours

[@SebastianDaschnerIT]

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

[@weremarc]

Using graalvm from docker fallback is very slow in macOS with M1. Better install graalVM in this case.

[@MegaWurzelpeter]

Thanks for the very informative video. Unfortunately my work environment is still in the ages of Eclipse RCP and POJO applications :-/

[@TheVladBlog]

Reduce the volume of the intro and boost the volume of your speech…. My ears bled

[@SebastianDaschnerIT]

Thanks for pointing out, will do in the future