GraalVM, CRaC, Leyden and friends - in search of TRULY cloud-native Java
summary
GraalVM compiles Java ahead-of-time into standalone binaries that start instantly but breaks dynamic classloading and reflection unless classes are whitelisted or traced; Spring has special support. AppCDS saves prebuilt class data to cut startup. CRaC checkpoints a running JVM and restores it (AWS Lambda SnapStart uses this) but must replace nondeterministic sources like Random. Leyden proposes pipelines that combine GraalVM AOT produces standalone binaries, CRaC snapshots (AWS Lambda SnapStart) restore pre-initialized JVM state, and Leyden coordinates AOT, AppCDS and CRaC so teams can choose tradeoffs.
AI-written summary · about
chapters (9)
- 0:00Cloud-native Java challenges
- 3:18Java truly cloud-native today?
- 5:30Java in containers basics
- 10:55Cold start problem in Java
- 15:09GraalVM cloud-native runtime
- 23:42GraalVM tradeoffs and limits
- 26:53Startup optimization with CRaC
- 33:54Project Leyden future
- 37:05Conclusion and Q&A
related talks
46mGraalVM, CRaC, Leyden and friends - in search of TRULY...
26mGoing Serverless With Spring’s Support for GraalVM, Project CraC & More
01h 00mStatic Java, GraalVM Native and OpenJDK
48mRevolutionizing Java-based Applications with GraalVM.
46mCRAC vs GraalVM
50mBinary Java: CDS, CRaC and AOT for faster JVM startup and warmup
51mAOT: Everything you need to know about GraalVM for Java applications
50mGraalVM for Java developers