3 ms·
"Node for Rust" is a good way to think about it! From what I know about Akka, I believe Akka does more than Tokio. For example, Akka manages a supervision tree
by carllerche 7y ago
"Node for Rust" is a good way to think about it!
From what I know about Akka, I believe Akka does more than Tokio. For example, Akka manages a supervision tree. I believe Akka is trying to be more of an actor system where as Tokio is just trying to provide an asynchronous runtime for Rust.
- karmakaze 7y agoYes, it's confusing that Akka does both Futures and Actors (that it's well-known for). I've used and really liked Akka Futures so would probably much like Tokio.
- AtlasBarfed 7y agoIsn't node a single threaded event loop, while this and Go use multiple threads and queues to support multiple threads and processors? They even went into that with the comparison with Seastar. If this is better than Seastar, someone should start on porting ScyllaDB to Rust. Does Rust have a userspace TCPIP stack like Seastar? I think that is the other major advance Seastar uses for speedup.
- karmakaze 7y agoNode (like browsers now) have Worker Threads though I haven't used the Node ones myself.