The Future of Serverless Java
summary
Java currently powers ~12 million developers and ~80% of enterprises yet only ~5% of serverless functions use it; the gap narrows by concrete changes: class data sharing (application CDS on by default in Java 12) and jlink cut runtime sizes to ~30MB, GraalVM’s native-image provides AOT binaries for millisecond cold starts at the cost of some reflection, and the six‑month JDK cadence plus Panama and Project Portola improve container and native interop. Cloud support lags (AWS Lambda defaults to Java 8).
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:20Java Specification, Implementations, Virtual Machine, Ecosystem
- 5:124.96% of functions are Java 8??
- 6:47The Serverless Experience
- 7:35Trade-offs and the Ergonomic JDK
- 11:30AOT Ergonomics
- 13:08Java SE Modules
- 14:03Custom Runtime
- 15:01Respect the Environment Ensure that JVM Ergonomics chooses appropriate settings
- 15:13Docker Respects Resource Limits The JDK honors the Docker CPU settings
- 15:48JVM Container Awareness
- 16:12Project Portola
- 18:38The Desire for Simplicity
- 20:55Local Variable Type Inference
- 21:43Text Blocks (Preview)
- 23:09Switch Expressions
- 25:20Java: 1995 to 2017
- 28:45Cloud Platform Support
- 29:37Lighter-Weight Frameworks
related talks
48mJava in the Serverless Space
53mAdapting Java for the Serverless world
36mServerless Java
46mServerless Java: Challenges and Triumph
01h 15mJava in Serverless — To Be or Not To Be?
01h 03mKeynote: Why The Future of Java in the Cloud is Serverless
51mAdapting Java for the Serverless world!
56mThinking in Serverless Java (Code)
