Talks

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.
Tim te Beek
Moderne
Tim te Beek is a staff software engineer at Moderne, which automates software refactoring at scale. He has extensive experience contributing to and presenting on Open Source software within the Java ecosystem. Previously he worked as a consultant specializing in migration engineering and developer productivity.
Merlin Bögershausen
Moderne Inc
Merlin is a software engineer, architect and Oracle ACE with over 10 years of experience in various domains and languages. As a migration engineer, he helps teams and individuals utilize new features and assists with migration. In addition to development, speaking at conferences and being a dad, he teaches people how to land gliders (yes, I'm a flight instructor!) and plays volleyball.