Java in 2025: LTS Release, AI on JVM, Framework Modernization


Transcript:

2025 was not a quiet year for Java. The Java platform and the ecosystem around it continued to evolve rapidly, so let’s look at the major updates of the year.

Java turned 30 this year, which in tech terms usually means becoming a legacy fossil. But that did not happen. Java keeps adapting, modernizing, and still runs a large portion of the world’s critical infrastructure.

Java 25 is the new long-term support release. It brings numerous updates and 18 JEPs with new, improved, or revised functionality. LTS releases are the ones teams adopt and run in production for years, so this is a release worth checking out if you haven’t already. Among the important features are continuous improvements to Java Flight Recorder with better visibility and lower overhead, scoped values that move Java toward safer and more reliable concurrency with fewer thread-local risks, and the ahead-of-time cache from Project Leyden that improves startup and warm-up times. This is especially important for cloud-native and serverless environments. Compact object headers also reduce the memory footprint of Java applications. If you want a deep dive into every single JEP, check out my dedicated video on Java 25 features.

AI on the JVM kept gaining momentum in 2025. This year it crossed the line from an interesting experiment to something actually usable in production. The first production-ready version of Spring AI reached general availability in 2025. It provides a familiar programming model for integrating LLMs, vector stores, and AI workflows into Spring applications. LangChain4j was also very active this year and reached its first general availability release, bringing structured AI workflows to Java with a focus on strong type safety and JVM-friendly abstractions. Embeddable is a new project from Rod Johnson, the founder of Spring, aimed at building advanced AI agents on the JVM. It demonstrates that serious AI orchestration on the JVM is absolutely possible.

Kotlin 2.2 continued refining the language, tooling, and compiler performance. It also improved multiplatform support across web, server, and mobile. Kotlin’s popularity keeps growing, and it now stands shoulder-to-shoulder with Java in backend development. Kotlin also owns the multiplatform story across platforms. According to general feedback, KotlinConf 2025 felt very backend-focused, with a lot of attention on performance tooling and real-world use cases.

The Spring Framework team was also very busy this year. There were numerous releases across the Spring ecosystem, with Spring Boot 4 and Spring Framework 7 standing out. These releases modernized the ecosystem with cleaner APIs, better performance, and closer alignment with newer Java versions.

Quarkus released a new LTS version, 3.27, reinforcing its position as a serious choice for cloud-native Java applications with fast startup times, low memory usage, and aggressive optimizations. Apache Flink 2 marked a major shift in real-time data processing, introducing new asynchronous models and improved APIs that make streaming systems more powerful and expressive.

Vaadin merged Hilla into Flow, simplifying its ecosystem and reducing fragmentation. Vaadin 25 focused on being slimmer, faster, and more modern. The Micronaut framework continued refining its ecosystem around HTTP, messaging, security, and observability, with better OpenTelemetry integration and support for modern Java and Kotlin versions. Ktor kept gaining traction as a lightweight, Kotlin-first framework, continuing to improve its HTTP engine, coroutine-based concurrency model, and plugin system.

IntelliJ IDEA added support for Java 25 and Spring Framework 7, keeping pace with the ecosystem and making upgrades easier. JetBrains also introduced a new unified IntelliJ release strategy, simplifying versioning and making it easier to stay up to date. The Spring Debugger saw significant improvements in 2025, providing better insights into Spring applications at runtime without additional libraries or agents. JetBrains Research introduced LitmusKT, a testing tool for Kotlin multiplatform concurrency that helps uncover subtle concurrency issues that are otherwise very hard to reproduce.

Gradle 9 landed with a strong focus on performance and reliability. Builds are faster, more predictable, and better suited for large, complex projects. The configuration cache is now the preferred path in Gradle, delivering major speedups that are especially important for CI pipelines. OpenTelemetry continued evolving its stabilization and release practices, increasing confidence that today’s instrumentation will not break tomorrow.

BellSoft introduced hardened container images that are a strong fit for enterprise Java applications. These minimized images are based on Liberica JDK and Alpaquita Linux. They provide an immutable component set, up to 95% fewer vulnerabilities, and a single SLA from one vendor that covers the OS, runtime, and vulnerability management.

These were the major updates in and around the Java ecosystem in 2025. Of course, this is only the tip of the iceberg. There were many more releases across tooling, frameworks, and platforms. It was a busy year for Java, and we are looking forward to another year full of progress and innovation. If you enjoyed this video, don’t forget to like it, subscribe to the channel, and until next time.

Summary

2025 was a highly active year for Java, marked by the release of Java 25 as a new LTS and significant progress across performance, concurrency, and cloud-native capabilities. AI on the JVM matured from experimentation to production-ready solutions with Spring AI, LangChain4j, and new JVM-focused AI orchestration projects. Kotlin continued to strengthen its position alongside Java, while major frameworks like Spring, Quarkus, Micronaut, and Vaadin delivered substantial updates. Tooling and infrastructure also evolved, with improvements in IDEs, build systems, observability, and container security. Overall, the Java ecosystem remains modern, relevant, and well-positioned for the future.

About Catherine

Java developer passionate about Spring Boot. Writer. Developer Advocate at BellSoft

Social Media

Videos
card image
Jan 13, 2026
Hibernate: Ditch or Double Down? When ORM Isn't Enough

Every Java team debates Hibernate at some point: productivity champion or performance liability? Both are right. This video shows you when to rely on Hibernate's ORM magic and when to drop down to SQL. We walk through production scenarios: domain models with many-to-many relations where Hibernate excels, analytical reports with window functions where JDBC dominates, and hybrid architectures that use both in the same Spring Boot codebase. You'll see real code examples: the N+1 query trap that kills performance, complex window functions and anti-joins that Hibernate can't handle, equals/hashCode pitfalls with lazy loading, and practical two-level caching strategies. We also explore how Hibernate works under the hood—translating HQL to database-specific SQL dialects, managing sessions and transactions through JDBC, implementing JPA specifications. The strategic insight: modern applications need both ORM convenience for transactional business logic and SQL precision for data-intensive analytics. Use Hibernate for CRUD and relationship management. Use SQL where ORM abstractions leak or performance demands direct control.

Videos
card image
Dec 24, 2025
I Solved Advent of Code 2025 in Kotlin: Here's How It Went

Every year, Advent of Code spawns thousands of solutions — but few engineers step back to see the bigger picture. This is a complete walkthrough of all 12 days from 2025, focused on engineering patterns rather than puzzle statements. We cover scalable techniques: interval math without brute force, dynamic programming, graph algorithms (JGraphT), geometry with Java AWT Polygon, and optimization problems that need constraint solvers like ojAlgo. You'll see how Java and Kotlin handle real constraints, how visualizations validate assumptions, and when to reach for libraries instead of writing everything from scratch. If you love puzzles, programming—or both—and maybe want to learn how to solve them on the JVM, this is for you.

Further watching

Videos
card image
Jan 29, 2026
JDBC Connection Pools in Microservices. Why They Break Down (and What to Do Instead)

In this livestream, Catherine is joined by Rogerio Robetti, the founder of Open J Proxy, to discuss why traditional JDBC connection pools break down when teams migrate to microservices, and what is a more efficient and reliable approach to organizing database access with microservice architecture.

Videos
card image
Jan 27, 2026
Sizing JDBC Connection Pools for Real Production Load

Many production outages start with connection pool exhaustion. Your app waits seconds for connections while queries take milliseconds; yet, most teams run default settings that collapse under load. This video shows how to configure connection pools that survive real production traffic: sizing based on database limits and thread counts, setting timeouts that prevent cascading failures, and implementing an open source database proxy Open J Proxy for centralized connection management with virtual connection handles, client-side load balancing, and slow query segregation. For senior Java developers, DevOps engineers, and architects who need database performance that holds under pressure.

Videos
card image
Jan 20, 2026
JDBC vs ORM vs jOOQ: Choose the Right Java Database Tool

Still unsure what is the difference between JPA, Hibernate, JDBC, or jOOQ and when to use which? This video clarifies the entire Java database access stack with real, production-oriented examples. We start at the foundation, which is JDBC, a low-level API every other tool eventually relies on for database communication. Then, we go through the ORM concept, JPA as a specification of ORM, Hibernate as the implementation and extension of JPA, and Blaze Persistence as a powerful upgrade to JPA Criteria API. From there, we take a different path with jOOQ: a database-first, SQL-centric approach that provides type-safe queries and catches many SQL errors at compile time instead of runtime. You’ll see when raw JDBC makes sense for small, focused services, when Hibernate fits CRUD-heavy domains, and when jOOQ excels at complex reporting and analytics. We discuss real performance pitfalls such as N+1 queries and lazy loading, and show practical combination strategies like “JPA for CRUD, jOOQ for reports.” The goal is to equip you with clarity so that you can make informed architectural decisions based on domain complexity, query patterns, and long-term maintainability.