Pimp your Jakarta EE applications
summary
A small full‑stack REST app with CDI, JPA and PostgreSQL migrates from Java EE 8 to Jakarta EE 10 by applying OpenRewrite recipes that rename javax. to jakarta. and update persistence.xml properties, then builds and runs on lightweight runtimes: a provisioned WildFly Bootable Jar (hollow jar) and on Quarkus where the app folder is ~36 MB, cold start is ~3 s, dev reload ~1.5 s, optional native 50 ms startup exists, and dev services spawn temporary Postgres containers; everything shown is open source.
AI-written summary · about
chapters (16)
- 0:00Introduction to talk
- 1:29Modernizing Jakarta EE apps
- 2:13Demo application overview
- 6:08Migrating to Jakarta EE 10
- 8:19OpenRewrite migration tool
- 13:48Traditional app server model
- 17:19Jar server runtimes
- 20:11WildFly bootable JAR demo
- 26:55Micro runtime frameworks
- 27:17Quarkus introduction
- 31:34Migrating to Quarkus
- 35:18Quarkus startup demo
- 38:08Configuration profiles
- 41:21Dev Services feature
- 42:02Migration benefits summary
- 47:31Resources and Q&A
related talks
45mEverything YOU need to Know About Jakarta EE 10
50mJakarta EE 10: Modern & Lightweight Cloud Application Development
55mModern and Lightweight Cloud Application Development with Jakarta EE10
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
48mJakarta EE 10 Feature by Feature
40mJakarta EE 10 - Simplicity for Modern and Lighweight Cloud Applications
40mMigrating from Java EE to JakartaEE 10: Challenges and Opportunities
44mPaving the road with Jakarta EE and Apache TomEE