ljph

115 karma · joined November 24, 2016

ljph··on Show HN: Coerce – Distributed actor framework in Rust

A lot of progress has been made since I last submitted this project, back in 2019: https://news.ycombinator.com/item?id=21796753

- Remoting

- Clustering

- Sharding

- Persistence (redis connector & in-memory currently provided, more to come)

- Supervision

- Metrics

- Tracing

- Service Discovery (+ k8s)

And much more! :)

ljph··on Show HN: Coerce – Actor runtime for Rust using async/await and tokio channels

https://crates.io/crates/coerce-rt :)

ljph··on Show HN: Coerce – Actor runtime for Rust using async/await and tokio channels

Regarding data serialization, I'm currently using serde_json, however that's just because it's easy to work with for development/testing purposes though I do love the idea of using protobufs!

Node compatibility and I guess distribution overall are problems I'm extremely looking forward to tackling! :)

ljph··on Show HN: Coerce – Actor runtime for Rust using async/await and tokio channels

Hi mate,

The goal is to eventually have actors spread across multiple servers with automatic load balancing etc. I'm currently working on remote actors, with the goal for the API to be exactly the same whether you're talking to a local actor or a remote actor - it shouldn't matter to the user!

The runtime is just Tokio's runtime, actors are just tasks awaiting on messages (and handling them) from their Receiver!

Cheers!