On behalf of the Spring Boot team and everyone that has contributed, it’s my pleasure to announce that Spring Boot 2.1.0 has been released and is available now from repo.spring.io, Maven Central and Bintray. This release adds a significant number of new features and improvements. For full upgrade instructions and new and noteworthy features please see the release notes.
We’ve upgraded to the latest stable releases of other third-party libraries wherever possible. Some notable dependency upgrades in this release include:
- Hibernate 5.3
- Micrometer 1.1
- Reactor Californium
- Spring Data Lovelace
- Spring Framework 5.1
- Tomcat 9
- Undertow 2
As part of our ongoing efforts to improve performance, we’ve made some significant progress in Spring Boot 2.1. Applications will now start faster and consume less memory while they do so. This can be particularly beneficial in environments with very tight memory constraints.
We’ve also embraced Spring Framework and Spring Data JPA’s support for bootstrapping Hibernate asynchronously. If you use Spring Data JPA and set
spring.data.jpa.repositories.bootstrap-mode=deferred, Hibernate will bootstrap in a separate thread while the rest of your application’s startup processing proceeds in parallel.
Following on from Spring Framework 5.1’s support for Java 11, Spring Boot 2.1 now also supports Java 11 while also remaining compatible with Java 8.
If a property needs to express a size in bytes or similar convenient unit, it can expose a
org.springframework.util.unit.DataSize property. Similar to our
Duration support introduced in Spring Boot 2.0, the data size support allow a unit to be specified when configuring a value in
application.properties. For example,
10MB can be used for a value of 10 megabytes.
Two new Actuator endpoints have been introduced in Spring Boot 2.1:
/actuator/cachesprovides information about the application’s cache managers
/actuator/integrationgraphprovides a graph representation of Spring Integration components
The health endpoint has also be enhanced to allow a request for the health of an individual component to be made. For example, a request to
/actuator/health/db executes only the “db” HealthIndicator.
In addition to the upgrade to Micrometer 1.1, auto-configuration for exporting to AppOptics, Humio, and KariosDB has also been added. Metrics coverage has also been improved to include:
- Hibernate metrics
- Spring Framework’s WebClient
- Kafka consumer metrics
- Log4j2 metrics
- Jetty server thread pool metrics
- Server-side Jersey HTTP request metrics
There’s a whole host of other changes and improvements that are documented in the Release Notes. You can also find a list of deprecated classes and methods that we plan to remove in the next version.
If you’re interested in helping out, check out the “ideal for contribution” tag in the issue repository. If you have general questions, please ask at stackoverflow.com using the
spring-boot tag or chat with the community on Gitter.