A high-performance Rust library for building fault-tolerant, asynchronous actor-based systems that scale from local to distributed.
Kameo is a lightweight Rust library for building fault-tolerant, asynchronous actor-based systems. It simplifies concurrent programming by providing a robust actor model that integrates with Rust's async ecosystem, enabling developers to build scalable applications from microservices to embedded systems. The library abstracts complexities like async execution and failure recovery, allowing focus on business logic.
Rust developers building concurrent, distributed, or real-time systems such as microservices, web servers, data processors, gaming servers, chat applications, or embedded/IoT devices. It's suitable for those needing fault tolerance and scalable actor-based architectures.
Developers choose Kameo for its seamless integration with Rust's async ecosystem, built-in fault tolerance via supervision strategies, and support for both local and distributed communication using libp2p. Its lightweight design, type-safe interfaces, and panic safety make it a robust alternative for scalable actor systems.
Fault-tolerant async actors for Rust that scale seamlessly
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Leverages Tokio for efficient concurrency and integrates effortlessly with existing Rust async code, as highlighted in the README's compatibility claims.
Supervision strategies automatically recover from actor failures, ensuring system resilience without manual intervention, a key feature emphasized.
Supports both bounded and unbounded channels with backpressure management for load control, providing adaptability for various concurrency patterns.
Uses libp2p for peer-to-peer networking, enabling actors to communicate across networks with minimal setup, as demonstrated in the distributed actor examples.
Version 0.20 indicates it's not yet stable, so breaking changes are possible, which could impact production deployments despite its feature set.
Reliance on libp2p for distributed features adds dependencies and configuration complexity, which might be unnecessary or burdensome for purely local actor systems.
Compared to established alternatives like Actix, Kameo has fewer integrations, third-party plugins, and community resources, as hinted by the linked comparison blog post.