Bring the action: using GraalVM in production
summary
GraalVM native-image compiles a Spring Boot app (using the native-maven-plugin) into a standalone executable that drops JVM startup and cuts memory roughly 3–5x; a demo build analyzes 200,000 reachable classes, takes ~1m40s, and yields an idle process at ~136MB. Libraries work if they ship config, via the GraalVM reachability metadata repo, via framework-generated hints, or a tracing agent. Out-of-the-box throughput hits ~42k req/s vs JIT 50k, and optimized with PG/arch-specific flags reaches 58k req/s. Monitoring via VisualVM and Spring Actuator SBOMs is supported.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:07What is GraalVM Native Image
- 3:57Demo dictionary app
- 9:36Migrating existing apps
- 11:26Library compatibility
- 17:51Tracing agent for reflection
- 19:36Optimizing native executables
- 23:31Benchmarking demo
- 26:17Development strategies
- 27:41Security and monitoring
- 29:48Wrap-up and Q&A
related talks
46mBring the Action: Using GraalVM in Production
44mBring the Action: Using GraalVM in Production
46mFast and Lightweight Spring Boot Applications with GraalVM
47mBring the action: using GraalVM in production
45mGoing AOT: Everything you need to know about GraalVM for Java applications
53mBootiful GraalVM
44mNative Spring Applications with GraalVM
47mGoing Native: Fast and Lightweight Spring Boot Applications with GraalVM