Running Spring Boot applications as GraalVM native images
summary
Shows a working path to run Spring Boot as GraalVM native images using GraalVM native-image, SDKMAN, and the new Spring Graal Native experimental feature, with startup in under 1s for simple apps and a Hello World producing a sub-4MB Docker image. Reports roughly halved memory for small services (JIT ~200 MB vs native ~100 MB), explains JSON or agent-generated reflection config, build-time vs run-time init, long native-image builds, and differences between Community and Enterprise editions.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:46Umbrella project with a wide scope
- 5:44Class initialization
- 7:48Static configuration via JSON files
- 8:33Specifying static configuration
- 8:58Dynamic configuration via a Feature
- 11:36Spring MVC:relative CPU and memory profiles
- 14:00Java buildpack memory calculator
- 16:19Make sure to evaluate all the criteria
- 18:05Benchmarks
- 18:37Spring MVC: native versus JIT
- 21:03Spring with GraalVM native timeline
- 21:53spring-graal-native
- 22:33Spring portfolio rely on Framework abstractions
- 23:32Feature handling for Spring capabilities
- 25:34Spring WebFlux with Netty
- 26:10Spring MVC with Tomcat
- 28:30Spring roadmap
- 30:03(Native) test driven development
- 32:093rd party libraries
related talks
47mGoing Native: Fast and Lightweight Spring Boot Applications with GraalVM
40mThe Path Towards Spring Boot Native Applications on GraalVM
01h 12mThe path towards Spring Boot native applications
44mNative Spring Applications with GraalVM
53mBootiful GraalVM
46mFast and Lightweight Spring Boot Applications with GraalVM
51mMigrating Spring Boot apps to GraalVM
31mBring the action: using GraalVM in production