SkillsCast coming soon.
Many Java applications move to the cloud. But in the cloud, Java is often pricier than competitors like Go, Python, or JavaScript. Native Java with the static GraalVM Native Image AOT (Ahead-of-Time) compiler makes Java cheaper. Frameworks like Quarkus and Micronaut made native Java popular, and Spring Boot 3.0 just gave it a big boost. So, do I need to learn a new framework, like Quarkus or Micronaut? How does native Java work exactly? And when IS native Java now worthwhile for me?
My talk answers these questions. Here's a short summary: Native Java executables start much faster, require less memory, and are smaller and more secure. The downsides: Native Java doesn't always make business sense, doesn't work for all applications, often runs slower, and makes development and operations more complicated. And it's pretty new, so it's much harder to hire for and to troubleshoot.
My talk examines the advantages and disadvantages of native Java, independent of a particular Java framework. I explain how native Java works, when you can't use it, and how to get some of native Java's benefits in "regular Java". And I give you concrete guidelines so you can determine when native Java is worthwhile for you - and when it's not.