Keeping Up with the Java Release Train
summary
SIXT reports moving most services from Java 8 to Java 25 and rolling to 26 within days of release, claiming rolling upgrades every 6 months and measurable wins (about a 10–15% CPU drop on some services). The engineering model uses per-team automated tests, dependabot weekly updates for libraries, selective dependency choices, and platform work (Postgres, GC experimentation, AOT). A blocked transitive library is resolved by a runtime patch using a class file API agent instead of a costly fork, and upgrades now often build and deploy with trivial changes.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:58Modernizing an Over 100 Year-Old Organization
- 4:58Staying Current with Java's Release Cadence
- 14:33Building a Mature Deployment Pipeline
- 20:06Selecting Dependencies
- 25:30Using New Java Features
- 30:00Preparing for Future Java Versions
