Spring Boot 3 2 Spring 6 1

Spring Framework 6.1 and Spring Boot 3.2 run on Java 21, make concurrent programming simpler and more efficient with virtual threads, and initially support “Scale to Zero” startup time with CRaC. This TensorBlue analysis is based on reporting and source material from InfoQ (https://www.infoq.com/articles/spring-boot-3-2-spring-6-1/).

What Happened

InfoQ Homepage Articles Spring Boot 3.2 and Spring Framework 6.1 Add Java 21, Virtual Threads, and CRaC

Spring Boot 3.2 and Spring Framework 6.1 Add Java 21, Virtual Threads, and CRaC

Spring Framework 6.1 and Spring Boot 3.2 support Java 21, Java’s latest LTS version, while Java 17 remains the baseline.

The debut of virtual threads simplifies concurrent programming and makes it much more efficient, while there were improvements in reactive programming and Kotlin coroutines.

Coordinated Restore at Checkpoint (CRaC) is a new way of scaling to zero startup time in the JIT JVM, while scaling to zero with the existing GraalVM Native Image support got a considerable performance boost.

Spring Framework 6.2 and Spring Boot 3.4, scheduled for release in November 2024, will support Jakarta EE 11 and will be aligned with Project Leyden’s premain optimizations for faster startup.

Spring Boot, a popular framework for new Java applications, will turn 10 in April 2024, while its basis, the Spring Framework, will turn 20 one month earlier.

Spring Framework 6.1 (released on November 16, 2023) and Spring Boot 3.2 (released on November 23, 2023) run on Java 21. These releases will make concurrent programming simpler and more efficient with virtual threads, as well as improve reactive programming and Kotlin coroutines. For "Scale to Zero" startup time reductions, there is initial support fo

Oliver Drotbohm: Spring Boot 3 and Spring Framework 6 have been received extraordinarily well. We see enterprises upgrading to those versions both for their general infrastructure updates and their new features, such as the GraalVM support and dev services. That said, depending on the depth of the dependency on JakartaEE APIs, the package name changes can make this upgrade more challenging than previous ones. With Spring Boot Migrator and upgrade support within our tooling based on OpenRewrite, we try to help the community reduce that effort. The 2.7 generation is EOL, but luckily, Broadcom offers an extended commercial support service until August 2025.

InfoQ

Implications for Product and Engineering Teams

For TensorBlue readers, the useful question is not just what happened, but how this changes product architecture, engineering priorities, AI delivery, observability, team workflows, or executive decision-making.

• Review whether this changes your AI roadmap, platform architecture, or engineering operating model.
• Identify the specific workflow, reliability, governance, or developer-productivity lesson that applies to your organization.
• Convert the lesson into a small production experiment with measurable quality, latency, cost, adoption, or risk metrics.
• Document source assumptions clearly so teams do not overgeneralize from incomplete public information.

TensorBlue Takeaway

The practical opportunity is to turn this signal into a concrete implementation decision: better AI systems, stronger product instrumentation, more reliable automation, and clearer technical governance. Teams that connect public technology shifts to their own delivery systems will move faster without adding unnecessary complexity.