Book Image

Supercharge Your Applications with GraalVM

By : A B Vijay Kumar
Book Image

Supercharge Your Applications with GraalVM

By: A B Vijay Kumar

Overview of this book

GraalVM is a universal virtual machine that allows programmers to compile and run applications written in both JVM and non-JVM languages. It improves the performance and efficiency of applications, making it an ideal companion for cloud-native or microservices-based applications. This book is a hands-on guide, with step-by-step instructions on how to work with GraalVM. Starting with a quick introduction to the GraalVM architecture and how things work under the hood, you'll discover the performance benefits of running your Java applications on GraalVM. You'll then learn how to create native images and understand how AOT (ahead-of-time) can improve application performance significantly. The book covers examples of building polyglot applications that will help you explore the interoperability between languages running on the same VM. You'll also see how you can use the Truffle framework to implement any language of your choice to run optimally on GraalVM. By the end of this book, you'll not only have learned how GraalVM is beneficial in cloud-native and microservices development but also how to leverage its capabilities to create high-performing polyglot applications.
Table of Contents (17 chapters)
1
Section 1: The Evolution of JVM
4
Section 2: Getting Up and Running with GraalVM – Architecture and Implementation
8
Section 3: Polyglot with Graal
13
Section 4: Microservices with Graal

Limitations of Graal AOT (Native Image)

In this section, we will go through some of the limitations of Graal AOT and native images.

Graal ahead-of-time compilation performs static analysis with the closed-world assumption. It assumes that all the classes that are reachable at runtime are available during build time. This has a direct implication on writing any code that requires dynamic loading – such as Reflection, JNI, Proxies, and so on. However, the Graal AOT compiler (native-image) provides a way to provide this metadata in the form of JSON manifest files. These files can be packaged along with the JAR file, as an input for the compiler:

  • Loading classes dynamically: Classes that are loaded at runtime, which will not be visible to the AOT compiler at build time, need to be specific in the configuration file. These configuration files are typically saved under META-INF/native-image/, and should be in CLASSPATH. If the class is not found during the compilation of...