Programming language: Rust
License: The Unlicense
Tags: Network Programming     Async     Message Queue     mqtt     iot    
Latest version: v0.31.0

RuMqtt alternatives and similar packages

Based on the "Network programming" category.
Alternatively, view RuMqtt alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of RuMqtt or a related project?

Add another 'Network programming' Package


NOTE: Archived. No further development under this repo.

Follow progress of a different implementation here

Build Status Documentation

Pure rust MQTT client which strives to be simple, robust and performant. This library takes an opinionated approach of spawning an eventloop thread where all the mqtt related network io happens. The eventloop takes care of necessary robustness tasks without user having to rethink of all the necessary stuff to implement

Client APIs will communicate with the eventloop over a channel. Check the documentation for possible client operations



Asynchronous. New publishs/subscriptions doesn't have to wait for the ack of the previous message before sending the next message. Much faster when compared to synchronous calls

Backpressure based on inflight queue length slow networks

Outgoing and incoming streams operating concurrently doesn't mean internal mqtt state buffers grow indefinitely consuming memory. When the inflight message limit is hit, the eventloop stops processing new user requests until inflight queue limit is back to normal and the backpressure will propagate to client calls.

The same is true for slow networks. The channel buffer will nicely smoothen latency spikes but a prolonged bad network will be detected through backpressure.


A lot of managed brokers will allow messages only at a certain rate. Any spikes and the broker might disconnect the client. Throttling limit will make sure that this doesn't happen. This is true even for retransmission of internal unacked messages during reconnections.

Automatic reconnections

All the intermittent disconnections are handled with automatic reconnections. But the control to do or not do this is with the user

  • On-demand disconnection and reconnections
  • Inbuilt JWT auth for SAAS brokers like GCP iotcore
  • Tls using RustTLS. Cross compilation and multi platform support is painless
  • Automatic resubscription. Not usually necessary when clean_session=false but might help when opensource brokers crash before saving the state
What's not supported
  • [ ] Cancelling mqtt will with disconnect packet