Serverless Java with Spring
summary
Shows how to run Spring apps on AWS Lambda using the AWS Serverless Java Container adapter that converts API Gateway JSON into Servlet requests so existing Spring Boot controllers run without rewriting; explains the Spring Cloud Function model for vendor-agnostic handlers and routing (static via env var, dynamic via HTTP header or custom callback). Demonstrates cold-start fixes: SnapStart cuts cold-start times ~80% (example from ~7s to ~1s) and describes GraalVM native-image as a lower-memory, faster-start alternative plus Hikari/CORGI checkpoints for DB reconnection.
AI-written summary · about
chapters (13)
- 0:00Serverless Java with Spring
- 1:06Serverless computing basics
- 2:10Containers vs serverless
- 6:47Functions vs containers
- 8:52What is a function
- 13:28Spring Cloud Function
- 18:45Deployment models
- 24:47Adapting Spring Boot apps
- 31:33Performance and cold starts
- 36:07Optimizing with SnapStart
- 41:23GraalVM for Java
- 44:16Resources and next steps
- 45:00Q&A
related talks
42mScale Your @Controller to Zero with AWS Lambda or Azure Functions
44mHow to develop, run and optimize Spring Boot 3 application on AWS Lambda
51mServerless Spring
34mThawing Java on AWS Lambda
47mScale your @Controller to zero with AWS Lambda or Azure Function
24mHigh Performance Serverless Functions in Scala
53m"Serverless" Is What J2EE Was Meant To Be
36mServerless Java