Scale to Zero with Spring + GraalVM or WebAssembly
summary
Spring Boot 3 compiles Kotlin/JVM apps to a GraalVM native image that starts in milliseconds, uses far less memory and yields tiny container layers; demo shows the pet‑clinic native image starting ~0.3s startup vs 25s for the JVM on a tiny Azure instance. An experimental path compiles Kotlin to WebAssembly: Kotlin/Wasm + KoWasm produces ~130KB WASM artifacts run via WASI/nodejs, promising architecture‑independent, scale‑to‑zero deployments but still experimental.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:32Why scaling to zero?
- 1:02Intermittent use cases
- 5:56Typical deployment of a Spring Boot JVM application
- 6:26Deploying a Spring Boot native application
- 7:20Benefits of Spring Boot native applications
- 8:41Huge collaboration on reachability metadata
- 9:44Going native from a Spring Boot 2 application
- 15:14Comparing JVM and native on low resource Cloud hosting
- 18:03Security
- 18:23Open standard
- 20:11System languages
- 20:43Scripting languages
- 21:15Modern statically typed languages
- 22:03Enabling WasmGC support
- 23:44Competitive runtime footprint and performance
- 25:13Compose for Web
- 36:50WASI and Component Model roadmap
- 39:07What's next?
related talks
28mUsing GraalVM in the context of Kotlin
47mSpring Boot Revisited with KoFu and JaFu
47mThe best runtime for Kotlin is obviously GraalVM, isn't it?
40mKotlin on CRaC – new JVM features to speed things up
27mState of Kotlin Support in Spring
51mServerless Kotlin with App Engine
45mWhy Spring Loves Kotlin
18mGo full-stack with Kotlin or Dart on Google Cloud