rabble
rabble copied to clipboard
Clustered, location transparent actor library in Rust
It's effectively single threaded anyway.
A process can only handle one type of message. It isn't generic over many messages. This will change the API a bit, but shouldn't be too bad.
There are a bunch of incorrect links. Also, since rust 1.15, rabble no longer requires nightly.
We must be able to serialize and deserialize interned strings to allow distribution. This may result in the need to implement `Serialize`and `Deserialize` manually for `Pid` if the interner doesn't...
It should have at least links to the architecture doc and user guide, like in the README.md.
We need to support rolling upgrade of nodes. And this means backwards and forwards compatibility of messages. We could do version negotiation, but this gets dirty real fast, so instead...
https://doc.rust-lang.org/std/panic/fn.catch_unwind.html
Detect overload via min latency on the executor channel. When the min latency increases past a bound, stop processing new requests or slow the acceptance rate. This will appear as...