Building The Upgrade Muscle with OpenRewrite at Tinder
summary
Tinder describes a four‑stage upgrade pipeline that moves from spreadsheets to fully automated PR generation, using OpenRewrite recipes to rewrite tests and frameworks, migrating JMockit to Mockito and moving Java 8→11→17→21 across ~1,000 microservices. A three‑person platform team runs 5–8 upgrades per year, saves what they estimate as hundreds of thousands to millions in effort by generating 30 PRs in one month across 12 repos, and now layers scripts and AI handles the fuzzy 20% like missing tests and odd edge cases.
AI-written summary · about
chapters (7)
- 0:00Tinder's upgrade philosophy
- 3:24The first manual upgrade
- 9:25Scaling through organization
- 19:02Automating with OpenRewrite
- 26:00Building the upgrade muscle
- 29:09Modernizing with AI agents
- 33:22Actionable upgrade playbook
related talks
13mModernize your money-maker
41mOpen Rewrite – Dive in Automated Refactoring
48mWeeding Your Micro Service Landscape
01h 17mRefactoring the ROI of Software
17mMajor migrations made easy
50mOpenRewrite: Refactor as Code
39mMoving fast and staying aligned how automation powers progress
13mMajor migrations made easy