Enterprise Java Migrations
summary
Team at Twitter is migrating JDK 8 to JDK 11 across services, running an internal OpenJDK-based JDK11 with patches and planning an incremental rollout over several months. Migration work concentrates on making builds and tests compatible, splitting concerns into runtime and testing vs build so teams can upgrade independently. A core team of about ten engineers prepares code, submits targeted patches and pull requests, and coordinates testing and scheduling to avoid a single big switch. Ongoing work, not finished yet.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:10Where do you work
- 3:07Marketing
- 3:45Migration Timeline
- 4:32How many people are involved
- 6:30One at a time
- 7:47Puzzles
- 8:14What do you think
- 8:28Conferences
- 8:50Chris Algieri
- 9:35Where is Nora from
- 10:08Outro
related talks
50mJava. Migrating to 11 in real app
53mA year with jdk11 in production.
46mGoing Java::Current in Production
53mApproaching the JDK 25 LTS release through real-world migration
50mHow We Migrated New Relic to Java 11
47mJava. Migrating to 11 in real app
29mFarewell to Java 8
41mSystematically migrate to newer Java version