Scale up with GraalVM and AWS Lambdas
summary
Claim: GraalVM native image cuts Lambda cold-starts and memory use. Measured setup times show the regular JVM ~20–29 ms, AWS SnapStart ~19 ms and GraalVM native image ~13 ms, with max memory ~52 MB for native vs ~90 MB for JVM/SnapStart. Built a custom runtime ZIP (native binary + bootstrap), used Docker to build on Amazon Linux and deployed via AWS CDK; the endpoints respond and logs confirm the timings and lower footprint.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 2:30What is GraalVM
- 6:02Native image benefits and limitations
- 13:52Debugging and framework support
- 16:23AWS Lambda overview
- 21:15Java demo setup
- 31:02Building GraalVM native image
- 33:39Infrastructure as code with CDK
- 43:00Deploying and testing functions
- 46:17Performance comparison results
- 50:40Final advice and summary
related talks
46mThawing Java on AWS Lambda Reducing Cold Start Times from 11 Seconds to 1
46mReduce Cold Starts for Java Serverless Applications in AWS
01h 03mServerless 2049
53mHigh performance Serverless Java on AWS
42mJava in the Cloud with GraalVM
44mJava In The Cloud with GraalVM
47mBring the action: using GraalVM in production
52mGraalVM native images explained