Trascritto

Legacy Java Modernization: Stop Fixing Legacy Java by Hand and Let AI Do It

29 nov 2025 · 21 min. 17 sec.
Legacy Java Modernization: Stop Fixing Legacy Java by Hand and Let AI Do It
Capitoli

01 · The Case for AI-Powered Java Modernization

0 sec.

02 · The Legacy Java Dilemma

26 sec.

03 · AI-Driven Modernization Process

1 min. 47 sec.

04 · The Assessment Phase: Exposing Technical Debt

4 min. 22 sec.

05 · Cloud Migration and Cost Optimization

12 min. 39 sec.

06 · The Results and Benefits of Automated Modernization

17 min. 6 sec.

07 · Closing Thoughts and Call to Action

20 min. 53 sec.

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ù
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 walks through a case where an AI agent assesses, upgrades to Java 21 and migrates to Azure with a full audit trail.

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

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.
mostra meno
Informazioni
Autore Mirko Peters M365, Azure & AI
Organizzazione m365 FM
Sito www.m365.fm
Tag

Sembra che non tu non abbia alcun episodio attivo

Sfoglia il catalogo di Spreaker per scoprire nuovi contenuti

Corrente

Copertina del podcast

Sembra che non ci sia nessun episodio nella tua coda

Sfoglia il catalogo di Spreaker per scoprire nuovi contenuti

Successivo

Copertina dell'episodio Copertina dell'episodio

Che silenzio che c’è...

È tempo di scoprire nuovi episodi!

Scopri
La tua Libreria
Cerca