Evaluation of MQTT Bridge Architectures in a Cross-Organizational Context

TL;DR

This paper investigates how different MQTT bridge architectures affect latency and reliability in cross-organizational IoT data processing, providing insights for optimizing deployment configurations.

Contribution

It benchmarks two MQTT bridge deployment options in a real-world IoT platform to analyze their impact on system performance and reliability.

Findings

Number of bridge components affects latency and reliability.

MQTT packet size influences data transmission performance.

Topic naming impacts system quality attributes.

Abstract

The latest surveys estimate an increasing number of connected Internet-of-Things (IoT) devices (around 16 billion) despite the sector's shortage of manufacturers. All these devices deployed into the wild will collect data to guide decision-making that can be made automatically by other systems, humans, or hybrid approaches. In this work, we conduct an initial investigation of benchmark configuration options for IoT Platforms that process data ingested by such devices in real-time using the MQTT protocol. We identified metrics and related MQTT configurable parameters in the system's component deployment for an MQTT bridge architecture. For this purpose, we benchmark a real-world IoT platform's operational data flow design to monitor the surrounding environment remotely. We consider the MQTT broker solution and the system's real-time ingestion and bridge processing portion of the platform to be the system under test. In the benchmark, we investigate two architectural deployment options for the bridge component to gain insights into the latency and reliability of MQTT bridge deployments in which data is provided in a cross-organizational context. Our results indicate that the number of bridge components, MQTT packet sizes, and the topic name can impact the quality attributes in IoT architectures using MQTT protocol.