Bring the Action: Using GraalVM in Production
summary
GraalVM is used to run Spring apps either as a JDK or as an ahead‑of‑time native executable built with native‑image and Spring AOT; uploader cites 37% of Spring users evaluating or running native GraalVM and Alibaba runs native in production since 2020. A demo compiles a Spring app that analysis finds ~33k reachable types, ~50k fields and ~178k methods out of ~300k, producing a 120MB binary that starts in 148 ms startup (JVM start was 2.5s). Benchmarks show 53.7k RPS on JVM, 44k out‑of‑box native, 60k optimized native; memory typically 3x–5x less, builds use the native-image quick build mode, tracing agent and Micrometer monitoring succeed.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:05What is GraalVM
- 3:53JVM vs Native Image for Java
- 6:19Native Image compilation
- 8:07Demo: Spring app with GraalVM
- 10:55Demo: Spring to Native Image
- 15:58Native Image benefits
- 17:21Resource usage benefits
- 18:24Security benefits
- 19:46Framework compatibility
- 23:19Library compatibility
- 24:44Library best practices
- 32:00JVM vs Native Image performance
- 35:30Profiling Native Image
- 37:39Memory vs CPU usage
- 39:23Demo: Monitoring Native Image
- 41:51Cloud and observability
- 42:11Greener alternative
- 42:53Cross-platform builds
- 43:15Getting started
related talks
46mBring the Action: Using GraalVM in Production
31mBring the action: using GraalVM in production
47mBring the action: using GraalVM in production
50mGoing AOT: Everything you need to know about GraalVM for Java
46mFast and Lightweight Spring Boot Applications with GraalVM
45mGoing AOT: Everything you need to know about GraalVM for Java applications
47mGoing Native: Fast and Lightweight Spring Boot Applications with GraalVM
53mBootiful GraalVM