Andrea Peruffo on foojay.io - Friends of OpenJDK

Endive 1.0 Is Here: Wasm on the JVM Ships Under the Bytecode Alliance

Mon, 29 Jun 2026 00:11:00 +0000

A few weeks ago, we wrote about a new generation of Java libraries powered by WebAssembly. SQLite, QuickJS, Protocol Buffers, the Ruby Prism parser, all compiled to Wasm and shipped as regular JARs. No JNI, no platform-specific binaries. Wasm as an implementation detail.

Today, the runtime that makes it all work has its first official release under the Bytecode Alliance . Endive 1.0 is available on Maven Central.

What Shipped

Endive continues the work started as Chicory , the pure-Java WebAssembly runtime that has been powering this ecosystem since 2023. Same API, same community, same codebase. The move to the Bytecode Alliance is organizational, not technical. For details on the fork and governance, see the announcement article .

Foojay Podcast #98: The End of JNI Pain: How WebAssembly Is Quietly Replacing Native Libraries in Java

Mon, 15 Jun 2026 08:13:00 +0000

WebAssembly is already running inside Java applications, most developers just don’t know it yet. In this episode, Andrea Peruffo walks us through how WebAssembly is becoming the modern, safe alternative to JNI: letting you run Rust, C, and other native libraries directly on the JVM, without the crash risks, the per-platform distribution headaches, or the observability blackhole that JNI creates. From JRuby’s Prism parser to SQLite and Postgres running as pure Java bytecode, the use cases are real and the project Endive, under the Bytecode Alliance, is ready to explore.

A New Generation of Java Libraries Is Born: Wasm Becomes the Implementation Detail

Tue, 26 May 2026 13:00:47 +0000

If you’re running JRuby in production, you’re running WebAssembly. If TrinoDB is evaluating your Python UDFs, that’s WebAssembly too. If Microcks is running JavaScript dispatchers to route your mock API responses, WebAssembly is doing the work.

You didn’t install a native binary. You didn’t configure JNI. You didn’t cross-compile anything for your target platform. It just works, because the Wasm module is hiding inside a regular JAR on your classpath.