VMware offers training and certification to turbo-charge your progress.Learn more
In practice, that means we are archiving the Spring Native GitHub repository and moving it to the https://github.com/spring-attic organization. There will be no new release of Spring Native (based on Spring Boot 2.x) and we are encouraging all Spring Boot users to migrate to Spring Boot 3.x to leverage its official native support.
If you missed SpringOne keynote, be aware that the recording of the section dedicated to Spring Boot 3 native support is available in 2 parts.
Part 1 with Thomas Wuerthinger, the GraalVM project lead, about the win-win collaboration between Spring and GraalVM teams.
And part 2 with Sandra Ahlgrimm, Senior Cloud Advocate at Microsoft, is about running Spring applications in a scale to zero fashion on Azure.
The goal of each Spring experimental project is to reach the General Availability stage, and that's what Spring Native did with Spring Boot 3 native support. We were not sure to succeed given the level of quality expected from the Spring portfolio and the technical challenges we had to solve. But we did it!
So let's use this opportunity to celebrate this achievement with the Spring community and the Spring team which have been collaborating closely to make native a first class compilation target for Spring applications after 3237 commits, 330 pull requests and 2800 GitHub stars. This would have not been possible with all the useful feedback we got.
I would like to send a special thank you to Andy Clement who contributed most of the project initially, and to Stéphane Nicoll and Brian Clozel who where instrumental in making native officially supported in Spring Boot 3.
But let's also celebrate the fact that we now have the Gradle and Maven Native Build Tools plugins in order to provide support out of the box for various open source JVM libraries. So far Spring has been the most prolific contributor but we see an increasing number of other contributors in pull-requests coming to the GraalVM metadata reachability repository.
And the best part of it is that Spring Boot 3 does not require any GraalVM substitution to patch Spring or JVM libraries. The code you run is the code of your open source library, which means better security, better debuggability and better maintainability.
Let's not forget all the energy we have put in introducing an extensive integration testing infrastructure that has materialized via the spring-aot-smoke-tests project that allow to track the status of the AOT and native support for a wide range of use cases.
Thanks to its Ahead-of-Time transformation engine, the quality of the native support provided by Spring Boot 3 is already significantly better than with Spring Native, but is obviously not perfect so we are continuing to increase the scope of the support in each Spring Boot patch releases with improvements in the various projects of the Spring portfolio. And we are excited to be able to benefits from upcoming GraalVM native image compiler and tooling improvements.