Cloud-Native Applications with GraalVM
summary
GraalVM Native Image compiles Java into standalone native executables start in milliseconds with much smaller memory footprints and smaller packages than a JVM build; companies report CPU drops up to ~10% and lower GC pauses. Micronaut fits well because it does compile-time DI; build uses native-image, but reflection and proxies require config — Maven/Gradle plugins and library-supplied resources can auto-generate most of it. Use profile-guided native builds (run in JIT, capture profile, rebuild) to regain peak performance, plus economy mode for faster local builds and GitHub Actions for CI.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:00Open Source
- 2:34Difference from the Gdk
- 9:47How To Create a Native Image
- 15:25Memory Requirement
- 26:50Github Action
- 27:17New Builds
- 27:52Vs Code Extensions
- 33:06The Main Difference between the Community and the Enterprise Edition
related talks
50mCloud native Java microservices with GraalVM
47mGraalVM as a Platform for Cloud Native Java
33mCloud-Friendly Applications with GraalVM
42mJava in the Cloud with GraalVM
44mJava In The Cloud with GraalVM
52mGraalVM native images explained
46mGraalVM Native Image — Faster, Smarter, Leaner
49mSupercharge your Native Image applications
