Chasing the Grail
summary
Graal AOT/JIT removal from JDK 16 is not the end: developers can still build native images with Graal native-image, use Spring AOT + Spring Native to generate reflection/configuration ahead of time, and pick alpine musl images for tiny bases. Example builds: a typical Spring microservice JAR becomes ~37 MB as a native image, an almost-empty init binary is under 3 KB, and properly built Alpine native containers boot in ~120 ms. Tooling demonstrated: Liberica Native Image Kit, cloud-native buildpacks, async-profiler; native images shrink memory and startup while trading off runtime diagnostics and dynamic features.
AI-written summary · about
chapters (14)
- 0:00Start
- 5:57Sample Microservice
- 7:17Base/Parent Images
- 8:24Pull Time (100 Mbps)
- 8:59Uncompressed Size (disk)
- 12:02Cloud Native Buildpacks
- 14:17Liberica JDK Images
- 17:08Fabric8? Profiling?
- 21:32Early Access
- 24:41JDK 16
- 27:49Liberica Native Image Kit
- 29:55Enable Native Image Support
- 34:20Flexible build
- 36:25Use Alpine for the Build
related talks
51mGoing AOT: Everything you need to know about GraalVM for Java applications
45mGoing AOT: Everything you need to know about GraalVM for Java applications
50mGoing AOT: Everything you need to know about GraalVM for Java
46mGraalVM Native Image — Faster, Smarter, Leaner
53mBootiful GraalVM
47mBring the action: using GraalVM in production
44mSelf-contained Native Binaries for Java with GraalVM
40mThe Path Towards Spring Boot Native Applications on GraalVM