How We Migrated New Relic to Java 11
summary
New Relic moves its Java fleet to a Java 11–first baseline, migrating a thousand engineers’ services, switching to AdoptOpenJDK images and bumping build systems to Gradle 5. Measured wins include 30–40% heap reduction on string‑heavy services and better G1 behaviour; rollout reaches ~70%+ on OpenJDK and ~75%+ on Gradle 5. Pain points: ASM/bytecode tools and CI plugins require coordinated upgrades, Apache Cassandra nodes aren’t Java‑11 ready (Cassandra 4 is beta), Thrift needs codegen on Java 8, and seven regression reports yield five false alarms and two real investigations.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:56High-Level Product Architecture
- 9:38Bytecode Weaving
- 10:42Migration at Enterprise Scale
- 11:52Why Are We Going To 117
- 22:22Build Environment
- 24:14Maven Plugins
- 29:26Library Version Upgrades
- 32:24Grand Central & Container Fabric
- 47:16Future State Architecture
related talks
55mWhy You Should Migrate to Java 11 Right Now.
46mGoing Java::Current in Production
47mJava. Migrating to 11 in real app
53mA year with jdk11 in production.
46mBeam Me Up, Java! A Journey through Java LTS Versions 11 to 21
42mMoving to Java 17 in production
41mSystematically migrate to newer Java version
01h 16mHow the industry moves on from Java 8?