On behalf of the team and everyone who has contributed, it is my pleasure to announce the release of Spring Native 0.11, which provides native support for Spring Boot 2.6. This ambitious release is the result of five months of hard work by the Spring team, who have been working on a brand new architecture to bring Spring support for creating native executables with GraalVM to the next level. You can already try it on start.spring.io!
Learn more about Spring Native 0.11 and see it in action in this new Spring Tips video from Spring Developer Advocate Josh Long.
New Ahead-Of-Time Engine
The biggest change is undoubtedly the introduction of a new AOT engine that performs a deep analysis of your Spring application at build-time to transform and optimize your application and generate the required GraalVM native configuration. Those transformations are performed by Maven and Gradle Spring AOT plugins.
Taking a deeper look, the AOT engine evaluates conditions at build time in order to generate an optimized application context and Spring factories (the plugin system behind Spring Boot) specifically crafted for your application. In practice, that means:
- Less Spring infrastructure to execute at runtime
- Fewer conditions to evaluate at runtime
- Less reflection, since programmatic bean registration is used
The AOT engine infers the native configuration required to run your application as a native executable based on the beans identified as active, knowledge of the Spring programming model, and native hints bundled with Spring Native or provided by your application itself.
We want to give special thanks to Stéphane Nicoll who led the design and the implementation of this new AOT engine.
Reduced Memory Footprint
A key advantage of the AOT engine is that it supports smaller memory footprints for native executable because the native configuration is more accurate, less reflection is required, and less Spring infrastructure is required at runtime.
Spring Native 0.11 offers an average of between 20% and 26% footprint reduction compared to Spring Native 0.10! The following image shows data points for a few sample applications:
Startup times are 16% to 35% faster in Spring Native 0.11 compared to 0.10 because some processing has moved from runtime to build time. There is still room for improvement since we could not fine-tune Spring Boot and Spring Framework’s internal architecture in this minor version update.
The AOT engine is also much more accurate because it doesn’t try to analyze Spring annotations or the various types to replicate what Spring does at runtime. Instead, it forks a new process where it creates and introspects an application context at build-time (without starting it). That allows use of a subset of what Spring Framework does at runtime and works at the bean definition level, which is much more accurate.
Performing those optimizations at build time means that there is less runtime flexibility than with the regular Spring Boot auto-configuration model. You can still change the HTTP port or the log level of your application when running an already compiled Spring Boot application, but you cannot add new beans at runtime by using a profile, for example.
That’s why, on the JVM, the AOT mode is optional. That’s an optimization that you can use if it fits with your needs. On native (which is, by design, much less dynamic at runtime), it is mandatory. Also, keep in mind that conditions are evaluated at build time for now. We will likely make that more flexible in the future so that it should fit with most use cases.
The new engine offers a pluggable and modular architecture that users (like you, or the Spring project teams) can use to support various new features.
For example, see this implementation of the
BeanFactoryNativeConfigurationProcessor extension point, which automatically creates a class proxy ahead of time for beans annotated with
@Scope(proxyMode = ScopedProxyMode.TARGET_CLASS) :
NativeConfiguration extension point has been refined to offer an API by using
NativeConfigurationRegistry as well:
Those extensions points are defined and then discovered in
META-INF/spring.factories , so you can provide your own.
AOT Testing Support
A very significant part of our work on Spring Native 0.11 has been on implementing testing support for the AOT codepath, in order to bring native testing support to a whole new level. The result is a very significant increase in compatibility, with many more kinds of tests supported.
Combined with the great JUnit 5 native support provided by the Native Build Tools, it lets you run your Spring Boot, Spring Framework, or just plain JUnit tests, like on the JVM.
Unrelated to Spring, Mockito is not supported yet, but there is ongoing work to make it possible for it to work in the future.
AOT on the JVM
Performing AOT transformation on an application that will run on the JVM has two key benefits.
The first one is to be able to easily debug the code that will run on native on the JVM (main application or tests) in your IDE, for example.
The second advantage is better efficiency. At the moment, it provides around a 4% to 17% smaller footprint.
AOT mode also accelerates the application startup by 3% to 24% .
Note that, until now, we had no specific focus on JVM efficiency, so there may well be opportunities to improve in later releases.
Bellsoft Liberica NIK
Bellsoft Liberica Native Image Kit (NIK) is a native-image compiler distribution based on GraalVM open-source repository and Liberica JDK. As of Spring Native 0.11, it is used by default for Buildpacks native support, which is consistent with the JDK side, where Liberica JDK is used by default. It can also be installed locally by using its SDKMAN integration or by downloading and installing it.
Earlier this year, the team announced, together with BellSoft, that VMware customers who use the Liberica Native Image Kit can run their Spring applications as native executables and be confident that they are fully supported.
Spring Native 0.11 also gave us the opportunity to provide a new baseline based on Spring Boot 2.6.
GraalVM 21.3 provides support for both Java 11 and Java 17, and leverages conditional native configuration and other related refinements to allow a smaller footprint and better native support for the JVM ecosystem. The Java 8 flavor of GraalVM is not provided anymore since it is too old to be reasonably maintained, but you can still compile most Java 8 applications with the Java 11 flavor of GraalVM. Native Build Tools 0.9.8 is supported, and we continue our collaboration to refine and improve it.
Spring Boot 3 First-Class Native Support
I think that Spring Native 0.11 achieves its goal of providing a mature native option for Spring Boot. The Spring team can now focus on the next major step: refined native support as part of Spring Framework 6, Spring Boot 3, and related portfolio projects.
Keep in mind that all we did on Spring Native was done in close collaboration with other Spring projects but without deep architectural changes. With AOT and native becoming major themes of Spring Boot 3 and Spring Framework 6, the quality, maintainability, and ease of use of those features will reach a new level. The AOT engine will be refined and integrated directly into Spring Framework. Other projects, such as Spring Data or Spring Security, will be able to provide native support (and to test it) for their scope, and Spring Boot will provide out of the box AOT and native executables support in its plugins and documentation.
Our collaboration with the GraalVM team and the JVM ecosystem is going to increase in order to provide native configuration for various libraries outside of Spring, either in those libraries directly or in a native configuration repository directly integrated at the Native Build Tools level.
We plan to start providing GraalVM native support out of the box in Spring Boot 3 milestone 2, targeted for late March 2022, leveraging all that we learned while working on Spring Native. General Availability is planned for late 2022. We have lots of exciting plans ahead, but, for now, let’s take the time to celebrate this release with the members of the Spring team and of the Spring community who contributed. Cheers!