Migrating from Java EE: to Spring Boot or Something Else
summary
Migrating monolith Java EE apps to Spring Boot often takes far longer than planned—one client moves ~30% after six years—so consider alternatives: upgrade to a modern Jakarta server (GlassFish/Payara) or run lightweight services with GlassFish embedded to copy-paste existing JAX-RS/CDI code into microservices. Automated tooling handles most of the work: OpenRewrite plus Eclipse Transformer convert javax→jakarta and update dependencies to ~99% but require small manual fixes (PrimeFaces theme, XML descriptors). For cloud/native workloads, evaluate Quarkus or Piranha for fast startup and native images.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker background
- 1:05Survey on Java EE migration trends
- 3:12Challenges of migrating to Spring Boot
- 7:17Case study: Monolith migration struggles
- 14:47Options for modernizing Java EE applications
- 20:30Upgrading to Jakarta EE on new servers
- 24:08Automating Jakarta EE migration with tools
- 33:12Alternative: Jakarta EE microservices
- 39:54GlassFish Embedded for cloud deployments
- 41:20Quarkus and native compilation benefits
- 44:32Panama: A modular Jakarta EE runtime
- 55:20Summary and recommendations
- 56:04Q&A and closing remarks
related talks
48mMigrating From Java EE - to SpringBoot Or Something Else?
55mFrom Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
40mMigrating from Java EE to JakartaEE 10: Challenges and Opportunities
59mFrom Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
52mPimp your Jakarta EE applications
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
55mModern and Lightweight Cloud Application Development with Jakarta EE10
39mHow to Reduce the Footprint of Your Spring Boot Applications