Going Native: Trying Out AOT For Spring Boot

, Software Pundits
This post was originally published on this site

Apium Hub

Background

One of the key selling points for the Java programming language, when it was released, was the promise of “write once, run anywhere”. That is to say, that code written in Java would not need to be compiled into native code specific to an exact computer architecture. Instead, the Java code would be compiled into “byte code”, i.e. instructions that would be interpreted and executed by the Java Virtual Machine (JVM) that would be installed on the host computer. This provided the freedom in the software development process for Java developers – no need to maintain build machines for Linux, MacOS, Windows, etc – at the cost of reduced performance due to several factors, among others:

The intermediate step of the JVM interpreting and executing the compiled byte code. The JVM would itself need to initialize and begin to load/execute the code, i.e. a “cold start” that would

To read the full article click on the 'post' link at the top.