bastion VS ractor

How is this better / different than https://github.com/bastion-rs/bastion ?

There are attempts to implement an Erlang/BEAM-inspired reactor/runtime/executor/ecosystem for Rust's Async, in particular Bastion. (There are also Lumen, Lunatic and Async-Backplane/Async-Supervisor.)

I would be interested in an example showing how to build a robust runtime like bastion with fault tolerance.

But the issue you're referring to, building a fault-tolerant web server where you can have granular control over killing background jobs regardless if they're blocked on a syscall, totally requires using this kind of software architecture. See Bastion.

Bastion, a Rust async runtime inspired by the beam distribution and supervision model

I don't really know much about erlang, but I think this may be along the lines of what you are thinking of: https://github.com/bastion-rs/bastion

(I also don't really think the linux kernel people would be interested...)

This reminds me of bastion. Looks like it attempts to fulfill the same needs, though I guess Lunatic has native WASM support whereas bastion might require some tweaking to have it work? Haven't worked with bastion, so that part of harder time with WASM is just a wild speculation. On the other hand bastion looks much more mature. Probably /u/vertexclique could give a more informed opinion about the difference between the two ;) I really like what these projects are putting forward.

This project also appears interesting, but it seems that its clustering features have yet to be tested in large scale distributed systems.

https://github.com/slawlor/ractor/discussions/131

If you look at my comment history, you'll see I'm well familiar with the BEAM.

I'm in full agreement with you, but I'm not sure you need full robust process supervision trees to mimic what the BEAM does in the context of LiveView on a single machine.

I do want to say, I 100000% times prefer Elixir, it's tooling, ecosystem, web frameworks, easy of scaling vertically and horizontally, etc over Go or any other lang that probably do something analogous to LiveView via what ever concurrency primitives that language/runtime champions; Go with it's Communicating sequential processes(CSP) and Rust with the Ractor lib (https://github.com/slawlor/ractor).

Also consider an actor framework like ractor. You can have actors listening to sockets, who will then message subscribed actor or actors with the data.

github