Java. Migrating to 11 in real app
summary
Migrating two real Java server apps to Java 11 succeeds by focusing on concrete fixes: use Java Flight Recorder + Java Mission Control to prove ROI and find a hot producer causing allocations, replace illegal reflective setAccessible calls or add JVM flags like --add-opens, upgrade CI/Gradle/Maven and containers, and supply removed APIs (jaxb) as dependencies. Observed benefits include ~16% RAM drop from compact strings (reports up to 40%), faster startup with AppCDS, and compatibility across 8→9→11 in the demo.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 3:34JDK vendors and licensing
- 7:13Debunking migration myths
- 9:00Java versioning philosophy
- 12:43Key features and tooling
- 17:30Removed and deprecated code
- 20:50Modules and project Jigsaw
- 25:20Migration roadmap
- 29:00Handling illegal access
- 32:15Practical migration demo
- 36:17Advanced tools and conclusion
related talks
50mJava. Migrating to 11 in real app
55mWhy You Should Migrate to Java 11 Right Now.
46mGoing Java::Current in Production
50mHow We Migrated New Relic to Java 11
53mA year with jdk11 in production.
45mMigrating Java UI Client Applications to OpenJDK 11
46mBeam Me Up, Java! A Journey through Java LTS Versions 11 to 21
42mMoving to Java 17 in production