Java in the Cloud with GraalVM
summary
GraalVM Native Image compiles Java ahead‑of‑time into a single native executable and the demo shows concrete wins: a Micronaut app boots in 22 ms startup vs ~500 ms on the JVM (~25×), memory falls from ~200 MB to ~100 MB while throughput remains ≈109k req/s, and container images can shrink to about 6 MB container. It requires a build‑time native-image step, may need reflection JSON via the tracing agent, and must be built on the target OS/architecture.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:43What GraalVM offers
- 3:42GraalVM 🤝 Java microservice frameworks
- 4:10Java in the cloud - Goals
- 5:06Native image build process
- 7:04JIT vs AOT
- 8:48Low resource usage
- 9:56Example: Horizontal scaling of microservices
- 10:30Demo: Startup & performance
- 21:06Minimize vulnerability
- 21:17Reduced attack surface
- 23:29Demo: Reducing attach surface
- 28:26Scalable microservices with Helidon SE & Native Image
- 28:56Compact packaging
- 29:41Lightweight containerized applications
- 30:27What's the catch?
- 30:40GraalVM & reflection?
- 34:26Required build time step
- 37:42What's new in GraalVM?
- 38:17New monitoring features in GraalVM Native Image
- 39:11GraalVM community roadmap on GitHub
- 39:52What's next for Native Image?
- 40:34Get started with GraalVM
- 40:57Summary
- 41:44Outro
related talks
44mJava In The Cloud with GraalVM
50mCloud native Java microservices with GraalVM
47mGraalVM as a Platform for Cloud Native Java
52mGraalVM native images explained
33mCloud-Friendly Applications with GraalVM
35mCloud-Native Applications with GraalVM
34mFast and Efficient Java Microservices with GraalVM
47mBring the action: using GraalVM in production