Cloud native Java microservices with GraalVM
summary
GraalVM Native Image compiles Java apps ahead of time into a self‑contained executable that the demo shows as a 50 MB binary starting in 50–300 ms and using 50–100 MB RAM while the native-image build takes about 2–3 minutes on a dev machine. Micronaut integrates AOT config and a tracing Java agent can generate reflection/resource hints during tests. Expect smaller Docker images, optional static musl linking for FROM scratch containers, and tradeoffs: faster startup and lower footprint but potentially lower peak throughput than a fully warmed JVM unless using enterprise PGO optimizations.
AI-written summary · about
chapters (10)
- 0:00Introduction to GraalVM
- 2:29What is GraalVM
- 15:33Cloud-native Java with GraalVM
- 19:49Native Image build process
- 23:01Configuring native image builds
- 34:57Dockerizing native images
- 37:22Performance tuning native images
- 40:14Framework support overview
- 43:25Beyond web apps with GraalVM
- 45:31Q&A and resources
related talks
42mJava in the Cloud with GraalVM
47mGraalVM as a Platform for Cloud Native Java
35mCloud-Native Applications with GraalVM
33mCloud-Friendly Applications with GraalVM
44mJava In The Cloud with GraalVM
52mGraalVM native images explained
45mFast and Efficient Microservices with GraalVM
34mFast and Efficient Java Microservices with GraalVM
