Website |
Getting started |
Blog |
Contributing
Chicory is a JVM native WebAssembly runtime. It allows you to run WebAssembly programs with zero native dependencies or JNI. Chicory can run Wasm anywhere that the JVM can go. It is designed with simplicity and safety in mind. See the development section for a better idea of what we are trying to achieve and why.
Reach out to us: let us know what you are building with Chicory. Join our team Zulip chat with this invite link.
Get started now with the official documentation
There are a number of mature Wasm runtimes to choose from to execute a Wasm module. To name a few v8, wasmtime, wasmer, wasmedge, wazero etc.
Although these can be great choices for running a Wasm application, embedding them into your existing Java application has some downsides. Because these runtimes are written in C/C++/Rust/etc, they must be distributed and run as native code. This causes two main friction points:
If you're distributing a Java library (jar, war, etc), you must now distribute along with it a native object targeting the correct architecture and operating system. This matrix can become quite large. This eliminates a lot of the simplicity and original benefit of shipping Java code.
At runtime, you must use FFI to execute the module. While there might be performance benefits to doing this for some modules, when you do, you're effectively escaping the safety and observability of the JVM. Having a pure JVM runtime means all your security and memory guarantees, and your tools, can stay in place.
- Be as safe as possible
- In that we are willing to sacrifice things like performance for safety and simplicity
- Make it easy to run Wasm in any JVM environment without native code, including very restrictive environments.
- Fully support the core Wasm spec
- Make integration with Java (and other host languages) easy and idiomatic.
- Be a standalone runtime
- Be the fastest runtime
- Be the right choice for every JVM project
Chicory development was started in September 2023. The following are the milestones we're aiming for. These are subject to change but represent our best guesses with current information. These are not necessarily sequential and some may be happening in parallel. Unless specified, any unchecked box is still not planned or started. If you have an interest in working on any of these please reach out in Zulip!
- Wasm binary parser
- Simple bytecode interpreter
- Establish basic coding and testing patterns
- Generate JUnit tests from wasm test suite
- Make all tests green with the interpreter (important for correctness)
- Implement validation logic (important for safety)
- Draft of the v1.0 API (important for stability and dx)
- Decouple interpreter and create separate compiler and interpreter "engines"
- Proof of concept AOT compiler (run some subset of modules)
- AOT engine passes all the same specs as interpreter (stretch goal)
- WASIp1 Support (including test gen)
- SIMD Support
- in the interpreter
- Tail Call
- in the interpreter
- Exception Handling
- Multi-Memory Support
- GC Support
- Threads Support
- Chicory: A Zero Dependency Wasm Runtime for the JVM on Java Advent 2023
- Chicory - a WebAssembly Interpreter Written Purely in Java with Zero Native Dependencies on InfoQ
- Chicory: Write to WebAssembly, Overcome JVM Shortcomings on The New Stack
- Meet Chicory, exploit the power of WebAssembly on the server side! by Andrea Peruffo (Devoxx BE 2024)
- WebAssembly, the Safer Alternative to Integrating Native Code in Java on InfoQ
- Chicory: Creating a Language-Native Wasm Runtime by Benjamin Eckel / Andrea Peruffo (Wasm I/O 2024)
- Chicory, a JVM Native WebAssembly Runtime by Benjamin Eckel (Dylibso Insiders)