Migration from Old Java-EE App to Modern Cloud Native Apps
summary
A migration strategy to move thousands of 10–15 year old Java EE web apps at ABN Amro into cloud-native applications. The approach upgrades remote EJB2 → remote EJB3 → local EJB3 → dependency‑injection, replaces JNDI dynamic config with file-based properties and then property servers (Consul, KeyVault), and targets lightweight Jakarta EE apps runnable on WebSphere, Open Liberty, Spring Boot or Quarkus, enabling incremental, low‑risk deployments while considering JDK/GraalVM and cloud concerns.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:19Old Java-EE challenges
- 8:42Cloud-native benefits
- 15:16Demo: Service detection with decorators
- 22:36Migration testing strategies
- 28:00Liberty and Spring implementation
- 32:28Summary and Q&A
related talks
51mEscape from Legacy Hell: A Java App Cloud Transformation
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
14mApp modernization on AWS, described by engineers who have done it
18mMigrating Legacy Financial Systems to Cloud: Challenges and Best Practices
30mMigrating a monolith to Cloud-Native and the stumbling blocks
55mModernizing Legacy Code - While Not Bringing Down Prod
52mPimp your Jakarta EE applications
55mModern and Lightweight Cloud Application Development with Jakarta EE10