mqtt.org VS reduct-js

We will explore a Spin application that uses the MQTT trigger and deploy it to run on your Kubernetes cluster using SpinKube, whether on the edge or in the cloud. MQTT is a lightweight, publish-subscribe messaging protocol that enables devices to send and receive messages through a broker. Our Spin app will receive MQTT messages from sound devices that are at each booth and chart booth volume over time. The result is a visual graph of engagement at each booth.

RabbitMQ is an open-source message broker software that implements a handful of messaging protocols, originally the AMQP (Advanced Message Queuing Protocol), and also includes web-based ones such as STOMP (Simple Text Orientated Messaging Protocol), MQTT (Message Queuing Telemetry Transport), and WebSockets to decouple applications that share asynchronous data. RabbitMQ not only serves as an attractive messaging system choice due to its robustness and well-maintained open-source nature but also stands out for its ease of use and configuration. Before creating our first RabbitMQ instance and cluster, let's explore some fundamental concepts around messaging and check out some common use cases.

Mosquitto itself does not support cluster deployment, but it can be implemented through the backend, see MQTT server support for details.

'$' is a reserved prefix for internal topics, even if you subscribe with a single '#', the Broker will not send them to you unless you explicitly subscribe, like the common $SYS topics;

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.

This quick start guide will walk you through the process of installing and using the ReductStore JavaScript Client SDK to read and write data to a ReductStore instance.

When we call bucket.beginWrite we create an entry in the bucket if it doesn’t exist yet. Then we write data to the entry with the current timestamp. Now our MQTT data is safe and sound in the storage, and we can access them by using the same SDK.

Traditionally, we have aligned our official SDKs for Python, C++, and JavaScript with the latest API so that you can use the latest features.

JavaScript Client SDK

You can use this feature in a Python or JavaScript application by using the Python and JavaScript client SDKs.

we are pleased to announce the release of version 1.3.0 of the ReductStore SDK for JavaScript. This version supports the new features of ReductStore v1.3, including labels and content type.

Now that you have a basic understanding of how ReductStore works, you can start using it in your projects. You can find more information about the ReductStore JavaScript SDK here.

When we call bucket.beginWrite we create an entry in the bucket if it doesn't exist yet. Then we write data to the entry with the current timestamp. Now our MQTT data is safe and sound in the storage, and we can access them by using the same SDK.

ReductStore has released v1.2.0 of its JavaScript SDK. This update includes support for ReductStore API version 1.2 with the new Client.me method, which allows you to retrieve information about your current API token and its permissions.

If you've been using the Reduct Storage client-side SDKs for Python, JavaScript or C++ to interact with your storage instances, then you'll want to upgrade to the latest version. This week, all of our SDKs were updated to support Reduct Storage v1.1.0 with Token API. With this new release, we've made some important enhancements and bug fixes that will make your development experience smoother and more productive. So make sure you upgrade today!