Creating Cloud Native Capabilities Using the Latest Features from Java and the JVM
summary
Claim: the XVM design aims to host 10,000 apps per server by combining a message‑based service model, per‑service containers and object tagging to enforce tenancy and track allocations. Built items: a prototype compiler, a slow interpreter for proof‑of‑concept, and a plan to emit LLVM/WASM for production. Key JVM features used are virtual threads → fibers mapping, scoped values for logical‑thread state, and records for tuples; prototype is stable but production implementation and GC tagging (some C required) are not finished.
AI-written summary · about
chapters (17)
- 0:00Java as top choice
- 3:51Ultra-dense autonomic cloud
- 7:53JavaScript not a fit
- 11:47Execution stacks and fibers
- 15:43Threads vs virtual threads
- 18:54Services and architecture
- 21:43Cloud-native XVM language
- 23:53Fibers and services async
- 26:45Fibers map to Java threads
- 27:49Coloring fibers for control
- 31:51Scoped values and thread infection
- 33:59Records simplify Java
- 35:48Class file API strategies
- 36:51Safe points and GC in XVM
- 37:33Cloud memory challenges
- 39:21Containers and security model
- 42:54Q&A: Readiness vs Erlang
related talks
45mCloud Native JVM. Cloud Runtime
55mWhat's new for Java in clouds?
52mCloud Native JVM. Cloud Compiler
42mBuilding Bulletproof Concurrent Applications on the JVM
51mYour next JVM: Panama, Valhalla, Metropolis
35mJava at Speed: Building a Better JVM
47mGraalVM as a Platform for Cloud Native Java
45mMinimal Values Under the Hood