Escape from Legacy Hell: A Java App Cloud Transformation
summary
A monolithic Java enterprise app with 2.5M+ LOC and 600k motor records moves from WebSphere/RMI and an Eclipse RCP rich client to Liberty, Vaadin front end, Camunda and cloud CI/CD; the team migrates 300k lines of UI code over three years and converts 1,000+ RMI interfaces to REST, shifts repos and pipelines to GitLab then Azure, creates per-PR ephemeral test environments, and reduces releases to biweekly while cutting infrastructure cost and manual installs.
AI-written summary · about
chapters (22)
- 0:00Introduction and speakers
- 2:13About the insurance policy system
- 6:33Legacy architecture overview
- 8:44Pain points of the old system
- 9:28Environment and deployment struggles
- 10:52CI challenges with Jenkins
- 12:19Migration challenges and goals
- 13:04Switching from RMI to REST
- 13:26Frontend transformation to Vaadin
- 16:01Backend migration to Liberty profile
- 17:48DevOps methodology implementation
- 20:36Developer experience improvements
- 21:40Current cloud architecture
- 23:05On-demand test environments
- 24:06Release process and frequency
- 26:31Migration to Azure and Kubernetes
- 27:57Benefits of infrastructure as code
- 30:00CI/CD vs continuous deployment
- 31:07Next steps: database migration
- 31:51Monitoring and automation plans
- 32:55Transformation impact and results
- 35:02Q&A session
related talks
38mMigration from Old Java-EE App to Modern Cloud Native Apps
30mMigrating a monolith to Cloud-Native and the stumbling blocks
14mApp modernization on AWS, described by engineers who have done it
18mMigrating Legacy Financial Systems to Cloud: Challenges and Best Practices
48mThe Journey of a strongly coupled Monolith into the Cloud Land
35mInnovation without compromise: better, stronger, faster Java in the Cloud
30mThis Old App, a guide to renovating apps for the cloud
27mThe journey from legacy to cloud - native success