Optimize your applications to the max with Jakarta EE and MicroProfile
summary
Shows how Jakarta EE plus MicroProfile produce thin WAR deployments that avoid fat JAR dependency conflicts, and how MicroProfile distributions run on lightweight runners in containers. Demonstrates swapping JVMs (HotSpot vs OpenJ9) and measures startup and memory: HotSpot uses ~1 GB at start and ~10 s startup while OpenJ9 cuts startup to ~3 s in the example. Covers reproducible Docker images, tuning knobs, and tradeoffs between fat artifacts and server-based deployments.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:11Jakarta EE foundations
- 6:13Programming model
- 10:16WAR deployment
- 13:54Standard specs
- 16:28MicroProfile cloud
- 19:50Quarkus models
- 21:00JVM performance
- 22:51Monitoring tuning
- 25:36Container images
- 28:54Dev-prod consistency
- 30:37Cloud-native focus
- 31:54Q&A
related talks
46mHow Class Data Sharing Can Speed up Your Jakarta EE Application Startup
46mSimple Tweaks to Get the Most Out of Your JVM
31mFast and Distroless Java in Containers: the Recipe!
05mInterview
49mJava and Containers Make it Awesome
57mCould your Java workloads be missing out on something?
55m10 strategies for developing reliable Jakarta EE & MicroProfile apps for the Cloud
45mEverything YOU need to Know About Jakarta EE 10