How to migrate the legacy project to Spring Boot
summary
Stepwise migration updates a large WAR to Spring Boot 4/4.1 using the Spring Boot Dependencies import and Cargo Maven plugin for automated Tomcat E2E runs, converting servlets to REST controllers and DB code to JPA + Spring Data while keeping Flyway; AI-assisted refactors produce an Uber war with lib provided Tomcat and reveal two small fixes (JVM version suggestion and a missing Flyway starter). Static singletons move to an ApplicationContext holder, commits and E2E tests stay green — migration completes incrementally; repo: https://github.com/seregamorph/petclinic-legacy, slides: https://miro.com/app/board/uXjVG7ZzHdE=/?share_link_id=493041505550
AI-written summary · about
chapters (19)
- 0:00Migrating legacy projects
- 1:10Why Spring Boot
- 3:15Legacy migration challenges
- 5:22AI for automated migration
- 7:08Migration planning steps
- 8:32Spring Boot version
- 9:16Spring Boot dependencies
- 11:27Running E2E tests after changes
- 12:49Spring Boot entry point
- 15:18Spring Boot in Tomcat
- 16:44Spring context accessors
- 18:51First Spring bean
- 20:15Migrating dependent beans
- 21:59Cyclic dependencies handling
- 23:02Servlet to annotations
- 24:30Uber WAR file
- 26:15Standalone run
- 28:01Finalizing migration
- 29:03Key takeaways
related talks
45mMajor migrations made easy
45mArchitecting your codebase
31mArchitecting your codebase
13mMajor migrations made easy
01h 04mMind the Gap: Jumping from Spring Boot 2.x to 3.x
29mFresh Wind for Legacy Software: How to Put Old Applications on New Feet
55mModernizing Legacy Code - While Not Bringing Down Prod
43mInside Spring: The Architecture Behind the Framework