Are you ready for Cloud Native Java?
summary
Cloud costs map directly to RAM hours, so concrete changes matter: switching to OpenJ9 cuts runtime heap size roughly 50–60% less heap versus HotSpot and often gives ~30% faster startup with its shared classes and AOT cache, which can be baked into Docker layers. Open Liberty yields ~100 MB server images and ~10s startup; MicroProfile adds config, fault‑tolerance, tracing, metrics and JWT so services can fallback, be observed and scale without monolith rewrites.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:36What's special about Cloud?
- 14:34The JVM saves the day
- 15:52What you run can outweigh the JVM benefits
- 18:48Not all cloud-native challenges can be solved by the runtime
- 20:50There's a good chance you'll use REST APIs.
- 24:24Handling 100s of collaborating services requires a strong operations focus
- 31:38Thank You
related talks
55mBoost Developer Productivity with Open Cloud Native Java
33mCloud Native Java with OpenJ9: Fast, lean and definitely mean
35mInnovation without compromise: better, stronger, faster Java in the Cloud
06mSimple Tweaks to Get the Most Out of your JVM
46mSimple Tweaks to Get the Most Out of Your JVM
49mJava and Containers Make it Awesome
01h 02mJourney to Cloud : Leave No Java Workload Behind
35mJava in a world of containers