Migrating From Java EE - to SpringBoot Or Something Else?
summary
Survey shows ~50% of installs still on WebLogic/WebSphere and many projects stuck on Java EE7/8; migrations routinely take far longer than planned (six‑month projects turn 12+ months) and one case keeps 60–70% monolith remains after six years. Options: keep/upgraded Jakarta runtimes or use embedded GlassFish in 3s to run existing WARs with minimal code changes, or move to Quarkus/Quarkus native via GraalVM or Piranha for subsecond starts; migration helpers include OpenRewrite/AI migrations.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 7:07Risks of migrating to Spring Boot
- 11:02Upgrade or migrate the server
- 16:26Modern Jakarta EE servers
- 23:28GlassFish embedded demo
- 27:29Quarkus and native compilation
- 34:17Quarkus development experience
- 38:12Alternatives like Helidon and Pirania
- 41:29Conclusion and Q&A
related talks
01h 02mMigrating from Java EE: to Spring Boot or Something Else
52mPimp your Jakarta EE applications
40mMigrating from Java EE to JakartaEE 10: Challenges and Opportunities
05mJavaOne Shanghai: Bert Ertman
41mSystematically migrate to newer Java version
41mMigrating an Application from Jakarta EE to Quarkus
55mFrom Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
59mFrom Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE