|
Hi, I'm very new to both of these tools and both look very much awesome to me. But I'm not able to understand deeply what is difference between them except that the Lunatic target is wasm while Bastion stays in Rust. Could anyone help me to understand this better? Thanks in advance. |
Replies: 1 comment 2 replies
|
Hi @zmilan! The biggest difference to me is that Bastion's processes are just Rust Futures. This makes them extremely lightweight and fits perfectly into the existing Rust eco-system. But you can't do some of the stuff that Lunatic enables:
From the perspective of a process in Lunatic, it owns the whole memory. You can never read/write directly to the memory of other processes (not even through unsafe pointer dereferencing). |
|
Hi @bkolobara thanks for the explanation. This is exactly the type of information I was looking for. I'm looking forward to fining some good use case and start playing with Lunatic :) |
|
I didn't know about Bastion, but in 2023 it doesn't look like the project is still actively maintained. |
Hi @zmilan!
The biggest difference to me is that Bastion's processes are just Rust Futures. This makes them extremely lightweight and fits perfectly into the existing Rust eco-system.
But you can't do some of the stuff that Lunatic enables:
From the perspective of a process in Lunatic, it owns the whole memory. You can never read/write directly to the memory of other processes (not even through unsafe pointer dereferencing).