// the find
riker-rs/riker
Easily build efficient, highly concurrent and resilient applications. An Actor Framework for Rust.
Riker is an actor model framework for Rust, offering supervision hierarchies, pub/sub channels, message scheduling, and basic CQRS support. It targets developers who want Akka-style actor semantics in Rust without reaching for a full distributed system. Last meaningful activity was early 2024 and the project shows signs of stagnation.
Supervision tree is properly implemented — actors can restart, stop, or escalate failures up the hierarchy, which is the core value proposition of the actor model. The pub/sub channel system is a clean addition that avoids the usual spaghetti of direct actor references. The example set is genuinely good: hierarchy, selection, dead letters, and multiple supervision strategies are all covered with runnable code. Modular design means you can swap out CQRS and event sourcing as separate crates rather than pulling them in unconditionally.
Still requires Rust Nightly — in 2024 that's a meaningful tax for any production system, and the README is honest about it but offers no timeline to stable. The clustering roadmap (remote actors, TCP/UDP, CRDTs) has been 'in development' with no visible progress; if you need distribution you'll hit a wall fast. Async integration is built on `futures::ThreadPool` which predates the tokio ecosystem dominance — interop with `tokio::spawn` and `async/await` is awkward. At 1,071 stars and 64 forks with a January 2024 last push, the community is thin; if you hit a bug you're likely fixing it yourself.