WebAssembly and the Future of the JVM Ecosystem
summary
Shows concrete examples: QuickJs4J delivers a full QuickJS engine as a ~700KB pure-JAR Java dependency used inside Microcks; compiling protoc to Wasm shrinks bundled binaries from ~400MB down to ~90MB with a 1.3MB Protoc4J artifact; SQLite4J and PG Lite run databases as Wasm inside the JVM. A Java-native Wasm runtime Chicory compiles Wasm to Java bytecode, matches Wasmtime in benchmarks, and an AOT path Redline (via Cranelift compiled to Wasm) overcomes the JVM 8,000-byte method limit for near-native speed.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:53What is WebAssembly
- 5:32WebAssembly for servers
- 10:10Running JavaScript engines in Java with WebAssembly
- 14:54MicroX and dynamic scripting
- 17:03Open Policy Agent policies compiled to WebAssembly
- 20:41Protobuf compiler for Quarkus
- 23:31Syntax highlighting with WASM
- 27:23WASM applications on JVM
- 28:29Chicory WebAssembly runtime
- 31:24GraalVM Web Image with Chicory
- 33:52Performance challenges and Redline
- 36:20Redline compiler and Cranelift
- 39:10Future of WebAssembly on JVM
- 41:22Q&A
