Going Serverless With Spring’s Support for GraalVM, Project CraC & More
summary
Compares concrete results: a baseline Spring Boot app cold-starts in ~6.5 seconds and uses ~200 MB; a GraalVM native image cuts startup to ~400 ms and roughly quarters memory but native builds take ~3m30s and ~3.5 GB RAM so CI-based builds are recommended; Project CraC restores a warmed JVM to ~244 ms startup with no memory win and requires snapshot handling and extra OS capabilities; class data sharing gives smaller, safe 2–4× startup wins with a single flag and minimal trade-offs.
AI-written summary · about
chapters (12)
- 0:00Serverless introduction
- 5:18Serverless drawbacks
- 7:04Deploy Spring on Knative
- 10:13Spring startup slow
- 14:37GraalVM native images
- 24:45GraalVM trade-offs
- 27:59Spring GraalVM hints
- 29:05Project CRaC snapshots
- 34:37Class Data Sharing
- 38:15Project Leyden AOT
- 39:20Optimization comparison
- 40:23Resources and next
related talks
26mGoing Serverless With Spring’s Support for GraalVM, Project CraC & More
44mGoing Serverless with Spring Boot 3
23mBoost Java Application Efficiency and Slash Costs with GraalVM and Spring AOT
17mAdopting Java for the Serverless world
53mScale up with GraalVM and AWS Lambdas
01h 00mAdapting Java for the Serverless world
43mScaling Your Spring Boot App to Zero
36mRunning Spring in a Serverless Environment
