rumqtt
api-guidelines
Our great sponsors
rumqtt | api-guidelines | |
---|---|---|
34 | 32 | |
1,473 | 1,199 | |
4.6% | 0.8% | |
8.9 | 3.3 | |
9 days ago | about 2 months ago | |
Rust | ||
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rumqtt
-
New scalable, fault-tolerant, and efficient open-source MQTT broker
https://github.com/bytebeamio/rumqtt
Disclaimer: have not tried it myself. I was, however, considering using it to replace Mosquitto as a broker.
-
What MQTT crates for use in WASM are out there?
Other crates like https://crates.io/crates/paho-mqtt and https://github.com/bytebeamio/rumqtt are not available for browsers and do not compile to wasm.
- Announcing rumqttd v0.18.0: with improved performance and reduced binary size due to enhanced release profile, while featuring retained and will messages, will delay interval for MQTTv5 and other cool changes!
- Announcing rumqttd v0.17.0 with Shared Subscriptions and Subscription IDs adding up to better MQTTv5 support!
-
rumqttd now supports QoS2 and MQTT over websockets
Recently lot of new contributors showed interest, as well as contributed to rumqtt, so thank you so much everyone for your support <3 Feel free to discuss anything in comments, if you wish to contribute as well, you can look for `good-first-issues` ( or open new issues here )
- Rumqttd now supports MQTTv5 topic alias and message expiry
-
Announcing rumqttd v0.15.0 with MQTTv5 features like Topic Alias and Message Expiry
GitHub release - rumqttd-0.15.0
-
rumqttc 0.21.0 released with MQTT5 support
there is already an issue open for it: https://github.com/bytebeamio/rumqtt/issues/432. It is something that we would love to have, but not something in priority.
I wanted to let you know that rumqttc, a Rust MQTT client library, now supports several new features in MQTT 5 protocol. If you're not familiar with MQTT, it's a lightweight messaging protocol designed for IoT devices with limited resources.
-
Hey Rustaceans! Got a question? Ask here (15/2023)!
I know I should have asked this in their issues, but someone already did and didn't get a response. So I was not sure whether to create another issue, or comment in the same one (and not get a response as well?). So I decided to ask on Reddit first, thank you! https://github.com/bytebeamio/rumqtt/issues/598
api-guidelines
- Best practices for designing traits in public crates?
-
Functional Options Pattern in Go and Rust
Just wanting to let this here for some further input: - https://rust-lang.github.io/api-guidelines/ - https://rust-unofficial.github.io/patterns/ - https://deterministic.space/elegant-apis-in-rust.html
-
Hey Rustaceans! Got a question? Ask here (15/2023)!
The API guidelines will help you write nice APIs. Clippy will usually at least find some things, try running with -Wclippy::pedantic for a lot more messages. Also you can ask mentors for specific guidance. Hope that helps.
-
Naming traits
There has been some previous discussion on this here: https://github.com/rust-lang/api-guidelines/discussions/28
-
What is the proper guidance on using generics as parameters for an API
I'm currently writing an API and using the API guidelines book. On the Flexibility page, there's a section on using generics as function parameters to minimize assumptions. The issue that I'm having is that the only example it gives is std::fs::File::open. Specifically, I want to know what is the "standard" way to use generics as parameters?
-
Prefixes in name and Reexports
I search up in the rust-api-guideline, but no luck finding something like this. There used to be an Organization according to this thread, but upon digging the repo commits, it was deleted by this commit. "We can reintroduce this section if we come up with a way to give firmer advice here."
-
What are some good practices when writing rust?
public api of a library should follow Rust API Guidelines.
-
astro-float 0.6.6 arbitrary precision floating point library update
API was made compliant with Rust API Guidelines.
-
Picking Up Rust Before C With My Goals In Mind?
Finally, there's also the Little Book of Rust Books where you could look for tutorial materials or things like like Rust Design Patterns, Rust API Guidelines, and The Rust Performance Book. (See also rust-learning)
-
Learning rust
Rust API Guidelines: If you're planning on building libraries or APIs in Rust, these guidelines provide recommendations for designing and presenting APIs in the language. They're written by the Rust library team, based on their experience building the Rust standard library and other crates in the ecosystem.
What are some alternatives?
ntex-mqtt - MQTT Client/Server framework for v5 and v3.1.1 protocols
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
mqtt-broker - A tokio-based MQTT v5 broker written in pure Rust [WIP]
patterns - A catalogue of Rust design patterns, anti-patterns and idioms
mqtt-rs - MQTT protocol library for Rust
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
mosquitto - Eclipse Mosquitto - An open source MQTT broker
idiomatic-rust - 🦀 A peer-reviewed collection of articles/talks/repos which teach concise, idiomatic Rust.
futures-batch - An adapter for futures, which chunks up elements and flushes them after a timeout — or when the buffer is full. (Formerly known as tokio-batch.)
rust - Empowering everyone to build reliable and efficient software.
lora-rs - LoRa and LoRaWAN crates for End Devices
gdnative - Rust bindings for Godot 3