Endive: A JVM native WebAssembly runtime

Endive, a JVM-native WebAssembly runtime, has been officially announced, offering a zero-dependency solution for executing WebAssembly modules within Java environments. This development is significant for Java developers seeking to embed Wasm without the complexity of native code or FFI, enhancing security and portability.

Endive is a fork of Chicory, developed by Dylibso, Inc., and aims to provide a safe, simple, and fully JVM-compatible runtime for WebAssembly. Unlike existing runtimes such as V8, Wasmtime, or Wasmer, which are written in C, C++, or Rust and require native distribution, Endive operates purely within the JVM. This eliminates the need to distribute native binaries targeting different architectures and simplifies deployment.

The runtime is designed with safety and ease of integration in mind, supporting core WebAssembly specifications and Java interoperability. It is built to run in restricted environments where native code execution might be problematic, such as serverless platforms or containerized applications. The project has completed initial features including a binary parser, bytecode interpreter, and test suite compatibility, with ongoing development focusing on performance improvements and extended WebAssembly features.

Why It Matters

This development matters because it addresses key challenges faced by Java developers integrating WebAssembly: native dependency management and security concerns. By providing a JVM-native runtime, Endive enables more secure, portable, and straightforward deployment of WebAssembly modules, potentially broadening WebAssembly’s adoption in enterprise Java applications and server environments.

Furthermore, Endive’s design aligns with the trend toward zero-dependency runtimes and safer execution environments, making it relevant for organizations prioritizing security and simplicity in their software stacks. Its compatibility with existing Java ecosystems could accelerate the use of WebAssembly for extending Java applications or building cross-platform plugins.

Background

WebAssembly has gained popularity as a portable, secure bytecode format, with multiple runtimes like V8, Wasmtime, and Wasmer available for execution. However, integrating these into Java applications often involves native code, complicating distribution and reducing safety guarantees. Chicory, the predecessor to Endive, was a pure Java implementation but lacked some features and performance optimizations. Endive builds on years of development, starting from Chicory, aiming to become the default WebAssembly runtime for Java without native dependencies. The project is part of a broader movement toward safer, more portable WebAssembly runtimes tailored for enterprise and server-side use cases.

“Endive is designed to run WebAssembly modules entirely within the JVM, eliminating native dependencies and simplifying deployment.”

— Dylibso, Inc.

“Our aim is to make WebAssembly execution seamless and secure on any JVM environment, including restrictive or cloud-native setups.”

— Endive developers

What Remains Unclear

It is not yet clear how Endive’s performance compares with existing native runtimes under heavy workloads. The project’s roadmap indicates ongoing development, including support for advanced WebAssembly features like SIMD, tail calls, and multi-memory, but these are still in progress. Additionally, adoption by the wider Java community remains to be seen, and integration with popular frameworks is still under exploration.

What’s Next

Next steps include further development of performance optimizations, extending WebAssembly feature support, and releasing stable API versions. The team plans to gather community feedback and encourage early adoption among Java developers. Monitoring how Endive performs in real-world applications and its integration with existing Java tools will be key milestones.

Key Questions

How does Endive differ from other WebAssembly runtimes?

Endive operates entirely within the JVM, avoiding native dependencies, unlike other runtimes like V8 or Wasmtime that require native code. This simplifies deployment, enhances security, and makes it suitable for restricted environments.

Can Endive run all WebAssembly modules?

Endive supports the core WebAssembly specification and has completed initial compatibility tests. Support for advanced features like SIMD and tail calls is in development, so some complex modules may require future updates.

Is Endive production-ready?

Endive is currently in early release stages with ongoing development. While it is functional for many use cases, organizations should evaluate its stability and feature completeness for their production needs.

How can I get started with Endive?

Developers can access the project’s documentation and join the Zulip chat for community support. The project’s GitHub repository is the primary source for downloads, updates, and contribution opportunities.

Source: Hacker News