The nervous system of Spring Framework
summary
Explains how Spring’s dependency injection and application context get materialized, how CRaC creates a disk checkpoint of the live context so all beans are preloaded and restart time drops to near-zero, and how GraalVM native images rely on ahead-of-time compilation that forces register reflection at build time. Describes concrete tradeoffs: CRaC restores break live sockets and external I/O, Graal requires explicit configuration for reflection and proxies, and each approach speeds startup but introduces specific runtime limits.
AI-written summary · about
related talks
26mGoing Serverless With Spring’s Support for GraalVM, Project CraC & More
46mCRAC vs GraalVM
41mGraalVM, CRaC, Leyden and friends - in search of TRULY cloud-native Java
01h 13mSpring: Your next Java microframework
53mJava on CRaC: Superfast JVM Application Startup
51mJava on CRaC Superfast JVM Application Startup
44mFrom Spring Native to Spring Boot 3
31mBring the action: using GraalVM in production