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
Feb 6, 2026
Backend Developer Roadmap 2026: What You Need to Know

Backend complexity keeps growing, and frameworks can't keep up. In 2026, knowing React or Django isn't enough. You need fundamentals that hold up when systems break, traffic spikes, or your architecture gets rewritten for the third time.I've been building production systems for 15 years. This roadmap covers three areas that separate people who know frameworks from people who can actually architect backend systems: data, architecture, and infrastructure. This is about how to think, not what tools to install.

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.

Further watching

Videos
card image
Feb 27, 2026
Spring Developer Roadmap 2026: What You Need to Know

Spring Boot is powerful. But knowing the framework isn’t the same as understanding backend engineering. In this video, I walk through the roadmap I believe matters for a Spring developer in 2026. We start with data. That means real SQL — CTEs, window functions, normalization trade-offs — and understanding what ACID and BASE actually imply for system guarantees. Spring Data JPA is useful, but you still need to know what happens underneath. Then architecture: microservices vs modular monolith, serverless, CQRS, and when HTTP, gRPC, Kafka, or WebSockets make sense. Not as buzzwords — but as design choices with trade-offs. Security and infrastructure follow: OWASP Top 10, AuthN vs AuthZ, encryption in transit and at rest, Docker, Kubernetes, Infrastructure as Code, and observability with Micrometer, OpenTelemetry, and Grafana. This roadmap isn’t about mastering every tool. It’s about knowing what affects reliability in production.

Videos
card image
Feb 18, 2026
Build Typed AI Agents in Java with Embabel

Most Java AI demos stop at prompt loops. That doesn't scale in production. In this video, we integrate Embabel into an existing Spring Boot application and build a multi-step, goal-driven agent for incident triage. Instead of manually orchestrating prompt → tool → prompt cycles, we define typed actions and let the agent plan across deterministic and LLM-powered steps. We parse structured input with Ollama, query MongoDB deterministically, classify risk using explicit thresholds, rank affected implants, generate a constrained root cause hypothesis, and produce a bounded containment plan. LLM handles reasoning. Java enforces rules. This is about controlled AI workflows on the JVM — not prompt glue code.

Videos
card image
Feb 12, 2026
Spring Data MongoDB: From Repositories to Aggregations

Spring Data MongoDB breaks down fast once CRUD meets production—real queries, actual data volumes, analytics. What looks simple at first quickly turns into unreadable repository methods, overfetching, and slow queries. In this video, I walk through building a production-style Spring Boot application using Spring Data MongoDB — starting with basic setup and repositories, then moving into indexing, projections, custom queries, and aggregation pipelines. You'll see how MongoDB's document model changes data design compared to SQL, when embedding helps, and when it becomes a liability. We cover where repository method naming stops scaling, how to use @Query safely, when to switch to MongoTemplate, and how to reduce payload size with projections and DTOs. Finally, we implement real MongoDB aggregations to calculate analytics directly in the database and test everything against a real MongoDB instance using Testcontainers. This is not another MongoDB overview. It's a practical guide to actually using Spring Data MongoDB in production without fighting the database.