web-console VS mqtt.org

Use token authentication to protect your data. You can generate an access token using either the Web Console or the CLI client.

You can manage the API tokens even with CURL, but the storage engine has an embedded Web Console which makes it easier.

Web Console

Moreover, we have released Web Console v0.5.0 with little improvements in the bucket management.

Now that we had a working battle-proven solution and approval, we kept working on the storage engine and its ecosystem. We promoted the project and grew our community. By September 2022, we already had Client SDKs for C++, Python , JavaScript and an embedded WebConsole. We stopped integrating new features into the experimental version 0 and started planing version 1.0 which should be ready for a commercial usage.

Today, I've released the next minor version of Reduct Storage Web Console. It doesn't have some big new features, but I did a few changes to improve its usability:

MQTT (optional): If you're aiming for advanced customization, familiarity with MQTT (a lightweight messaging protocol) will be beneficial for communicating between the toy and the server.

The MQTT protocol is widely used in IoT applications because of its simplicity and ability to connect different data sources to applications using a publish/subscribe model. While many MQTT brokers support persistent sessions and can store message history as long as an MQTT client is not available, there may be cases where data needs to be stored for a longer period. In such cases, it is recommended to use a time series database. There are many options available, but if you need to store unstructured data such as images, sensor data, or Protobuf messages, consider using ReductStore. It is a time series database specifically designed for storing large amounts of blob data and optimized for IoT and edge computing.

https://mqtt.org is more popular, but its more complex. You will unlikely write your own mqtt while you can easily write own stomp broker.

I wanted to share my latest package (published on NuGet) implementing the MQTT v5 protocol.

I jumped onto https://mqtt.org/ to try to answer my usual use-case question about non-Kafka messaging, which is: "Do the messages get saved anywhere so you can come back and read them later?" Still not entirely sure about it.

But I did see:

    This is why MQTT has 3 defined quality of service levels: 0 - at most once, 1- at least once, 2 - exactly once

rumqttd is a high performance, embeddable MQTT broker that we wrote in Rust. MQTT is extremely lightweight publish/subscribe messaging transport for the Internet of Things (IoT).