Speaker

Spring Boot 4 is here—but most organizations still run 2.x or 3.x across large, distributed codebases. Version drift happens, and it compounds over time. The good news: whether your next upgrade is 2.x → 3.5 or 3.5 → 4.1, the preparation steps are the same—and they’re the key to making any migration predictable and low-risk.

But Spring Boot 4 doesn’t travel alone. It brings Hibernate 7, Jakarta EE 11, Spring Security 7, and Java 17+ along for the ride. When you map out these dependencies, you start to see a metro map of interconnected upgrades—and suddenly it clicks why migrations require a coordinated, organization-wide approach rather than isolated team efforts. The same pattern applies to other large-scale changes on the horizon, like preparing for Post-Quantum Cryptography.

In this hands-on workshop, you’ll work with a realistic microservices environment: 8 interconnected Spring Boot services spanning older versions, shared libraries, and legacy dependencies. Using OpenRewrite—an open-source auto-refactoring tool—you’ll learn the staged workflow that platform teams use to prepare for major migrations.

AI is reshaping how we develop new software, as it's cheaper than ever to jump from an idea into an implementation. But how does that capability translate into maintaining software? Can we accelerate modernization, without introducing risk?

At OpenRewrite & Moderne we explore these topics daily together with some of the largest companies in the world. We'll share our lessons learned, and a practical approach to arrive at repeatable automations. We'll show how we analyze the scale of a migration challenge, generate a deterministic outline, expand that with dedicated automations, and finally close the loop for the last mile.

Join us for a practical real-world use case, with an approach you can adopt as well. Ideally everyone benefits from the collective efforts of community, determinism & AI to automate away toil, as we collectively accelerate how software gets produced & maintained.