ractor VS postcard

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

I've been enjoying postcard as a lightweight efficient binary serialization.

That said, postcard is not a self describing format (so everyone needs the same schema, no changes allowed), but I do have a tracking issue open for ways to handle this in the future.

For example, look at the Postcard serializer for inspiration.

Serde should be no_std, I have used it embedded with crates such as postcard. You can see how postcard disables default features of serde here : https://github.com/jamesmunns/postcard/blob/main/Cargo.toml

Another option that may work for some is SerDe on rust. You just write a struct with the fields you want #[derive(Serialize, Deserialize)] above it, and if codegens the functions to deserialize that struct from JSON and serialize it back. Example looks like this https://docs.rs/serde_json/latest/serde_json/#creating-json-by-serializing-data-structures (but you have to use serde-json-core if you don’t have an allocator). Can also easily reserialize to something small like postcard that’s meant for embedded storage.

https://github.com/jamesmunns/postcard

postcard seems like it would be particularly strong for the wasm use case as it produces small messages that are light in memory.