Enable Digital Sovereignty by Tech Stack Liquidity
summary
Claims a concrete migration path: OpenRewrite recipes perform semantic, testable code transforms (examples: JUnit4→5, logging stacks) and the platform runs them across repositories in parallel. Moderne precomputed LSTs cut execution to seconds by building a lossless semantic model; about 30 hours saved across 9 repositories appears in the demo. Recipes are deterministic but imperfect on day-one for closed-source edge cases, proprietary and Apache-2 variants exist, and orchestration produces ordered upgrade waves (e.g., Spring Boot 2.6→4.0) for safe rollout.
AI-written summary · about
chapters (7)
- 0:00Introduction to digital sovereignty
- 3:35What is digital sovereignty
- 6:24Tech stack liquidity explained
- 13:20OpenRewrite tool introduction
- 23:25Four dimensions of digital sovereignty
- 29:48Live demo of automation tools
- 40:05Key takeaways and Q&A
related talks
47mHow to Fix Your Technical Debt Dilemma
15mMajor migrations made easy
45mMajor migrations made easy
59mModernize Software and Tackle Tech Debt at Big Bank Scale
45mTrusting AI to Modernize Software at Scale
48mLegacy, for lack of a better word, is good
42mPrevent Rewrites - a Map from Legacy Ugliness to Modern DevSecOps
41mLegacy, for lack of a better word, is good