Zero Migration Java - Staying Current Without Breaking Your App
summary
Claim: upgrade the Java runtime without touching application code by using a modular, versioned runtime. Implements zero migration with Liberty modular features (feature versions are chosen in server.xml, runtime releases are single-stream and backwards compatible). Demo changes one number in build.gradle to pick a newer Liberty; live demo had network hiccups but recorded demo shows success. Production evidence: openliberty.io moves through 50 runtime versions, addresses 83 CVEs patched, adds 200+ feature versions and thousands of bug fixes with no regressions. Release cadence: 4-week releases, 5 years support.
AI-written summary · about
chapters (9)
- 0:00Introduction to Zero Migration Java
- 1:41The challenge of technical debt
- 3:24Why upgrades are so difficult
- 14:01What is zero migration?
- 16:07How Liberty implements zero migration
- 26:27Live demo of Liberty upgrade
- 36:05Real-world success with zero migration
- 38:16Modernizing with control
- 43:14Conclusion and Q&A
related talks
41mSystematically migrate to newer Java version
35mInnovation without compromise: better, stronger, faster Java in the Cloud
51mLife Beyond Java 8
47mModern Java: Change is the Only Constant
46mGoing Java::Current in Production
27mModern Java: Change is the Only Constant
50mJava. Migrating to 11 in real app
50mKeeping up with Java: Look at All These New Features!