Adopting Java for the Serverless world
summary
Claims that GraalVM native images cut cold starts to under <0.5s cold starts and shrink memory by excluding unused classes, but building a native image takes about 3.5 minutes for a simple function and requires a Linux executable and a custom runtime (extra overhead). Micronaut and Quarkus trade reflection for AOT-friendliness so they speed cold starts even without GraalVM; Quarkus offers a Maven native-image plugin while Micronaut currently lacks one for Maven, and Spring is still catching up via Spring Native with extra boilerplate.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:10Custom Lambda Runtimes
- 6:43AWS Lambda with Micronaut Framework
- 7:42Build GraalVM Native Image with Micronaut Frame
- 10:38Bean Registration with Spring Framework
- 15:15Project Leyden
related talks
33mCloud-Friendly Applications with GraalVM
55mQuarkus brings Serverless to Java developers
01h 00mAdapting Java for the Serverless world
50mCloud native Java microservices with GraalVM
39mAwesome Java applications with GraalVM and Java microservices frameworks
42mJava in the Cloud with GraalVM
52mGraalVM native images explained
53mEvolving Java for the Serverless Era with Micronaut
