Spring Boot 2.2.0 Released with Performance Boosts, Lazy Initialization, Java 13 Support, Immutable @ConfigurationProperties, and RSocket Integration
Spring Boot 2.2.0 has been officially released, offering faster startup, lower memory usage, optional lazy initialization via the spring.main.lazy-initialization property, full Java 13 compatibility, immutable @ConfigurationProperties through constructor binding, and extensive RSocket auto‑configuration with a new starter.
Spring Boot 2.2.0 is now officially available and can be downloaded from the Spring release repository or Maven Central.
Performance improvements : The new version starts up noticeably faster and consumes less memory, which is especially beneficial in environments with strict memory constraints.
Lazy initialization : Global lazy initialization can be enabled by setting the spring.main.lazy-initialization property, reducing startup time. However, this may increase request latency for lazily initialized beans and defer some startup‑time failures to runtime.
Java 13 support : Spring Boot 2.2 adds official support for Java 13 while maintaining compatibility with Java 11 and Java 8.
Immutable @ConfigurationProperties binding : Configuration properties now support constructor‑based binding, making @ConfigurationProperties classes immutable. Developers can annotate the class or a constructor with @ConstructorBinding and use annotations such as @DefaultValue and @DateTimeFormat on constructor parameters.
RSocket support : Comprehensive auto‑configuration for RSocket has been added, along with a new starter spring-boot-starter-rsocket . When spring-security-rsocket is on the classpath, Spring Security’s RSocket integration is also auto‑configured.
For the full list of changes, see the official release announcement: https://spring.io/blog/2019/10/16/spring-boot-2-2-0
Author: xplanet Source: oschina.net/news/110615/spring-boot-2-2-0-released
Architect's Tech Stack
Java backend, microservices, distributed systems, containerized programming, and more.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.