Boots Made for Walking: Spring Hygiene in the Enterprise
summary
Enterprise has ~40,000 Spring Boot repos (5k raw, 26k on JPMC boot, 9k on Chase Boot) and a ~10‑person core team; upgrades cost ~1 business day each and the math equates to ~400 full‑time equivalents per year without automation. The org adopts OpenRewrite recipes (minor releases every six months, monthly patch cadence), gets ~16.5k unique users, and moves supported apps from ~70% to 85% then back to 53% and recovers to ~67% by automating migrations and composing vendor + in‑house recipes.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:03Business case for upgrades
- 4:34JPMC Boot and enterprise context
- 7:21Inventory and measurement importance
- 9:51Benefits and risks of upgrades
- 15:53Spring Boot versioning model
- 21:29Reducing upgrade costs strategies
- 24:59Open Rewrite introduction and 2022 experience
- 30:55Open Rewrite results and impact
- 36:31Recipe development and maintenance
- 43:08Bulk execution and cultural considerations
- 47:17Summary and key recommendations
- 57:18Q&A session part 1
- 1:02:45Q&A session part 2
related talks
09mAjay Patel at SpringOne 2020
35mMachines Making Software
20m1 year of PaaS usage at SBB: lessons learned
01h 28mBehind the OSS curtain: How we manage Spring
52mLean Spring Boot Applications for the Cloud
01h 02mMigrating from Java EE: to Spring Boot or Something Else
01h 10mSpring Boot and JRebel
27mTransforming Traditional Enterprise Software Development Processes