MIMIC MQTT Simulator interoperates with major brokers

In addition to our prior published reports, we recently simulated
thousands of sensors to 3 more brokers

VerneMQ

RabbitMQ

EMQTT

with thousands of arbitrary messages per second published.

Regardless which broker you select, you can perform prototyping, scalability,
robustness and security testing of your IoT application with
MIMIC MQTT Simulator prior to deployment.

How is realistic MQTT testing with MIMIC different from simplistic testing?

Most simple test apps use a for loop to create connections to a MQTT broker,
using only one single IP address for a large number of client sessions.

By using one IP address per session with MIMIC MQTT Simulator just like in

real world scenarios (when do real sensors share IP addresses?) we
uncovered a flaw in third-party MQTT brokers.

They would fail after a small number of simulated sensors (typically 1000
connections).

Only after adjusting the ARP cache parameters on the broker systems did
we overcome this problem.

MIMIC allows you to create realistic IoT pre-deployment testing scenarios
using IPv4 or IPv6 addressing, just like in the real world.

MIMIC MQTT Simulator publishing synthetic load to HiveMQ

MIMIC MQTT Simulator is simulating 40,000 connected sensors.
The HiveMQ MQTT Broker connected with them as if they are physical
sensors. As shown in the graphs, MIMIC is generating messages at the
rate of around 4,000 messages / second.

In this scenario it has been running for many hours.
The 40001st connection is a third-party subscriber client. This shows
that MIMIC simulated sensors are no different than the real one.

MIMIC allows you to stage precise pre-deployment tests for HiveMQ and
other IoT applications to make sure they handle the expected load and
provide the needed performance. In addition, you can easily customize
message payloads of simulated sensors for rapid prototyping, and create
pathological scenarios to minimize risks.