Legacy Java Modernization: Stop Fixing Legacy Java by Hand and Let AI Do It
Scarica e ascolta ovunque
Scarica i tuoi episodi preferiti e goditi l'ascolto, ovunque tu sia! Iscriviti o accedi ora per ascoltare offline.
Legacy Java Modernization: Stop Fixing Legacy Java by Hand and Let AI Do It
Capitoli
Descrizione
Hand-upgrading legacy Java apps is slow, error-prone and leaves CVEs and idle cloud spend in place. This episode is for developers, platform engineers and IT leaders facing Java modernization. It...
mostra di piùIn this episode
- 00:00 – Why manual Java modernization fails
- 00:31 – The legacy stack and the modernization mandate
- 04:14 – Assessment: technical debt with receipts
- 08:36 – Automated upgrade from Java 8 to Java 21
- 12:38 – Cloud migration from AWS to Azure
- 17:09 – Results: time, CVEs, cost and hours
- 19:33 – Governance, audit trail and transparency
Key takeaways
- An AI agent can assess a legacy Java app end to end, building a dependency graph with CVE, upgrade-readiness, cloud-readiness and cost findings before touching code.
- The upgrade to Java 21 runs as an apply-build-test-patch loop with OpenRewrite recipes, BOM alignment, regenerated SBOMs and scanners, producing small reviewable commits.
- Migration to Azure App Service with Key Vault, managed identity and GitHub Actions approvals cut cost and CVEs together while every change stays traceable in Git.
Worth quoting
“Still hand upgrading legacy Java, that's not craftsmanship, that's unpaid penance. Manual modernization is a failure mode, slow, error prone and permanently behind.” – Mirko Peters (00:00)
“Most people think upgrading is cosmetic. Incorrect. You get cheaper concurrency and fewer stalls, directly visible in service level graphs.” – Mirko Peters (02:07)
Explore more on M365.FM
- Episode page: the full case study with chapters, quotes and FAQ on Java modernization
- AI agent – the agent that assesses, upgrades and migrates the legacy Java app with every change in Git
- Microsoft Azure – the migration target replacing AWS to consolidate billing, identity, policy and observability
- GitHub Copilot – named once as Copilot app modernization, the tool driving the case study
- Azure App Service – the recommended hosting target for a single Spring MVC app, versus Azure Spring Apps
- Related episode: Infrastructure as Code, DevOps & the Future of Azure with Maik van der Gaag [MVP]
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
Informazioni
| Autore | Mirko Peters M365, Azure & AI |
| Organizzazione | m365 FM |
| Sito | www.m365.fm |
| Tag |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
Commenti