Spring Boot and Cloud for Legacy Applications
summary
Legacy Spring 3.2 bookstore is migrated stepwise to Spring Boot and Spring Cloud config: a local config server is consumed by manually registering a bootstrap initializer, then by switching to the Spring Boot parent and starters. Key problems include an unexpected Jersey auto‑config init‑param collision (fixed by ordering/PriorityOrdered tricks), a breaking Jackson 1→2 change when moving to Spring 4.2, and missing Spring Boot Maven repackaging. Tests (an Mvc JSON controller test) stay green, dependency list shrinks roughly 50%, and the WAR runs after the fixes.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:54Defining the migration strategy
- 4:43Benefits and challenges
- 9:05Migration best practices
- 17:00Demo: Adding config client
- 25:54Demo: Troubleshooting and setup
- 31:58Demo: Introducing Spring Boot
- 38:19Demo: Upgrading dependencies
- 42:33Conclusion and Q&A
related talks
44mWhat's New in Spring Boot 2.0
01h 07mMigrating to Spring 4 from Spring 3 - What you need to know
51mLean Spring Boot Applications for The Cloud
59mFrom Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
01h 02mMigrating from Java EE: to Spring Boot or Something Else
51mHitting the “refresh” button on your Spring web application
51mSpring Boot 3 / Spring 6: What’s new?
49mJPoint 2023 TechRadar: Spring