nats.rs
An idiomatic Rust client for NATS, enabling secure, high-performance messaging in distributed and embedded systems.
What is nats.rs?
nats.rs is the official Rust client for NATS, a cloud-native messaging system. It provides a fully-featured, asynchronous interface for building distributed applications, microservices, and IoT solutions with high-performance, secure communication. The library supports core NATS, JetStream for streaming, and additional data storage APIs like Key-Value and Object Store.
Rust developers building distributed systems, microservices architectures, cloud-native applications, or embedded/IoT solutions that require reliable, high-throughput messaging.
Developers choose nats.rs for its idiomatic Rust design, compile-time safety features, and full NATS protocol support. It offers a performant, async-first client that integrates seamlessly with the Rust ecosystem, making it a robust alternative to other messaging clients in Rust.
Overview
Rust client for NATS, the cloud native messaging system.
Use Cases
Best For
- Building asynchronous microservices that need pub/sub or request-reply messaging
- Implementing event-driven architectures in Rust applications
- Developing IoT or embedded systems requiring lightweight, secure communication
- Creating distributed data pipelines with JetStream streaming capabilities
- Adding persistent key-value or object storage to Rust services via NATS
- Writing high-performance, cloud-native Rust backends with reliable messaging
Not Ideal For
- Teams using synchronous Rust codebases that avoid async/await patterns
- Enterprises requiring a messaging client with a stable, version 1.0+ API and guaranteed long-term support
- Projects with simple pub/sub needs where the overhead of NATS and its Rust client is unnecessary
- Applications not built on the Tokio async runtime, as nats.rs is optimized for Tokio
Pros & Cons
Pros
Built on Tokio, it enables high-performance, non-blocking messaging ideal for scalable cloud-native applications.
Supports Core NATS, JetStream for streaming, Key-Value Store, Object Store, and Service APIs, covering all NATS capabilities.
Uses Rust's type system to move connection options and other checks to compile time, reducing runtime errors.
Offers subscription iterators and APIs that align with Rust's ownership model, making it intuitive for Rust developers.
Cons
The crate is still on 0.x.x, so breaking changes may occur as the async ecosystem evolves, affecting stability.
Relies on dependencies like rustls that are also <1.0.0, which could introduce unexpected breaking changes.
Deeply integrated with Tokio, limiting flexibility for projects using other async runtimes like async-std.
Additional features and extensions are in a separate repository (Orbit), which may complicate maintenance and discovery.
Frequently Asked Questions
Related Projects
HurlHurl, run and test HTTP requests with plain text.
tonicA native gRPC client & server implementation with async/await support.
quiche🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
actixActor framework for Rust.
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.