How Netflix Is Upgrading to Spring Boot 3
summary
Netflix migrates about 3,000 applications and 1,500 libraries to Spring Boot 3 by making Java 17 the baseline and automating upgrades so developers do minimal work. A custom nebula-jakarta plugin stitches the Apache Tomcat migration tool with Gradle transforms to rewrite javax→jakarta at build time; OpenRewrite plus Gradle lint automates API and property changes. Early rollout shows ~300–400 apps upgraded with ~80% needing no manual fixes, and modular starters cut startup from ~30s to ~3s for batch jobs.
AI-written summary · about
chapters (12)
- 0:00Introduction and context
- 8:14Spring Boot 3 benefits
- 9:40Migration goals and strategy
- 11:46Jakarta EE 9 migration challenge
- 17:35Auto-configuration changes
- 21:34Automation tools and approach
- 24:27Java 17 adoption at Netflix
- 26:14Modernization and stack bets
- 28:18Modularity for performance
- 35:04Live upgrade demo
- 38:35Lessons learned recap
- 41:02Q&A session
related talks
53mHow Netflix Uses Java - 2026 Edition
48mHow Netflix Uses Java
45mNetflix’s Secret to Safe Automation at Scale
46mNext-Generation Cloud Native Apps with Spring Boot 3
42mBuilding and Deploying Netflix
55mFrom Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
51mSpring Boot 3 / Spring 6: What’s new?
59mFrom Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE