emqtt-bench VS mqtt.org

For installation and usage, please refer to emqtt-bench: Lightweight MQTT benchmark tool written in Erlang

git clone https://github.com/emqx/emqtt-bench.git cd emqtt-bench CMAKE_BUILD_TYPE=Debug BUILD_WITH_QUIC=1 make

With the help of the open-source MQTT performance test tool emqtt-bench, we test whether the client's Pub/Sub has a rate limit.

Originally published at https://www.emqx.com.

For deploying and running our cluster tests, we used AWS CDK, which allowed us to experiment with different instance types and numbers, and also trying out different development branches of EMQX. You can checkout our scripts in this Github repo. In our load generator nodes ("loadgens" for short), we used our emqtt-bench tool to generate the connection / publishing / subscribing traffic with various options. EMQX's Dashboard and Prometheus were used for monitoring the progress of the test and the instances' health.

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).