Java. Migrating to 11 in real app
summary
Two real Java server apps migrate to Java 11: compile with target 8, upgrade IDE/build/CI, add explicit modules (for example java.xml.bind moved to a dependency), replace Sun proprietary Base64 with java.util.Base64, and use SDKMAN to switch JDKs. Runtime fixes use --add-opens or module flags to silence illegal reflective access, and Flight Recorder + Java Mission Control diagnose a producer thread that causes heavy GC. One app saves ~4 GB of 24 GB heap (~16%); tests miss three invoice cases and require automated regression before rollout.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:36New release schema
- 10:37How to convince the business?
- 14:52Java Unified Logging
- 18:53Deprecated stuff
related talks
47mJava. Migrating to 11 in real app
55mWhy You Should Migrate to Java 11 Right Now.
46mGoing Java::Current in Production
53mA year with jdk11 in production.
45mMigrating Java UI Client Applications to OpenJDK 11
42mMoving to Java 17 in production
43mEngineering a Modern Java Platform
29mFarewell to Java 8