Lunatic is a universal runtime for fast, robust and scalable server-side applications. It's inspired by Erlang and can be used from any language that compiles to WebAssembly. You can read more about the motivation behind Lunatic here.
We currently provide libraries to take full advantage of Lunatic's features for:
If you would like to see other languages supported or just follow the discussions around Lunatic, join our discord server.
- Creating, cancelling & waiting on processes
- Fine-grained process permissions
- Process supervision
- Channel based message passing
- TCP networking
- Filesystem access
- Distributed nodes
- Hot reloading
We provide pre-built binaries for Windows, Linux and macOS on the releases page.
On macOS you can also use Hombrew:
brew tap lunatic-solutions/lunatic
brew install lunatic
To build the project from source you will need to have rustup installed:
# Add wasm32 compilation target
rustup target add wasm32-unknown-unknown
# Clone the repository
git clone https://github.com/lunatic-solutions/lunatic.git
# Jump into the cloned folder
# Build and install Lunatic
cargo install --path .
After installation, you can use the
lunatic binary to run WASM modules.
To learn how to build modules, check out language-specific bindings:
Lunatic's design is all about spawning super lightweight processes, also known as green threads or go-routines in other runtimes. Lunatic's processes are fast to create, have a small memory footprint and a low scheduling overhead. They are designed for massive concurrency. It's not uncommon to have hundreds of thousands of such processes concurrently running in your app.
Some common use cases for processes are:
- HTTP request handling
- Long running requests, like Websocket connections
- Long running background tasks, like email sending
- Calling untrusted libraries in an sandboxed environment
What makes the last use case possible are the sandboxing capabilities of WebAssembly. WebAssembly was originally developed to run in the browser and provides extremely strong sandboxing on multiple levels. Lunatic's processes inherit these properties.
Each process has its own stack, heap, and even syscalls. If one process fails, it will not affect the rest of the system. This allows you to create very powerful and fault-tolerant abstraction.
This is also true for some other runtimes, but Lunatic goes one step further and makes it possible to use C bindings directly in your app without any fear. If the C code contains any security vulnerabilities or crashes, those issues will only affect the process currently executing the code. The only requirement is that the C code can be compiled to WebAssembly.
It's possible to give per process fine-grained access to resources (filesystem, memory, network connections, ...). This is enforced on the syscall level.
All processes running on Lunatic are preemptively scheduled and executed by a work stealing async executor. This gives you the freedom to write simple blocking code, but the runtime is going to make sure it actually never blocks a thread if waiting on I/O.
Even if you have an infinite loop somewhere in your code, the scheduling will always be fair and not permanently block the execution thread. The best part is that you don't need to do anything special to achieve this, the runtime will take care of it no matter which programming language you use.
We intend to eventually make Lunatic completely compatible with WASI. Ideally, you could take existing code, compile it to WebAssembly and run on top of Lunatic; creating the best developer experience possible. We're not quite there yet.
Licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.