Repository files navigation

ARust client for theNATS messaging system.

Rust may be one of the most interesting new languages the NATS ecosystem has seen.We believe this client will have a large impact on NATS, distributed systems, andembedded and IoT environments. With Rust, we wanted to be as idiomatic as wecould be and lean into the strengths of the language. We moved many things thatwould have been runtime checks and errors to the compiler, most notably optionson connections, and having subscriptions generate multiple styles of iteratorssince iterators are first-class citizens in Rust. We also wanted to be alignedwith the NATS philosophy of simple, secure, and fast!

There are two clients available in two separate crates:

Async Tokio-based NATS client.

Supports:

• Core NATS
• JetStream API
• JetStream Management API
• Key Value Store
• Object Store
• Service API

The API is stable, however it remains on 0.x.x versioning, as async ecosystem is still introducing a lot of ergonomic improvements. Some of our dependencies are also consideredstable, yet versioned <1.0.0, likerustls, which might introduce breaking changes that can affect our users in some way.

Feature flags are Documented inCargo.toml and can be viewedhere.

Legacysynchronous client that supports:

• Core NATS
• JetStream API
• JetStream Management API
• Key Value Store
• Object Store

This client does not get updates, unless those are security fixes.Please use the newasync-nats crate.

Please refer each crate docs for API reference and examples.

Additionally Check outNATS by example - An evolving collection of runnable, cross-client reference examples for NATS.

Client extensions are available in separate repo under the umbrella project calledOrbit

We encourage all folks in the NATS and Rust ecosystems to help usimprove this library. Please open issues, submit PRs, etc. We'reavailable in therust channel onthe NATS slackas well!