Benefits of Native MQTT Integration on InfluxDB Cloud

This article was written by Kudzai Manditereza, Developer Advocate at HiveMQ. Scroll down for the author’s bio and photo.

Introduction

To a great extent, the value of the Internet of Things (IoT) is realized through the insights (data) generated from sensor data integrated in storage and analytics systems. Consequently, how the data integration is conducted directly impacts the success of IoT projects.

For this reason, InfluxData introduced Native Collectors to bypass multiple data hops and enable one-step integration of data from data brokers such as HiveMQ MQTT broker into its InfluxDB Cloud time series database.

MQTT-System-Architecture-Diagram-InfluxDB-Cloud

System architecture demonstrating how to bring MQTT Data to InfluxDB

In this article, I will discuss the seven benefits of Native MQTT data integration into InfluxDB Cloud.

1. Less complex IoT system architecture

Before Native Collectors, InfuxDB relied on Telegraf. This server agent sat between a HiveMQ MQTT broker and an InfluxDB Cloud Instance to format and relay data to the time-series database. While Telegraf is still helpful in complex scenarios, the possibility of eliminating this component and natively formatting data makes for a simplified IoT architecture for most use cases.

2. Reduced latency

Not all IoT applications are time-critical. However, some applications require data to land in your database within seconds to allow time for corrective action. In such cases, direct integration of the MQTT broker with your time series database can significantly save processing time that would have been incurred by having an additional hosting service in the middle.

3. Enforces interoperability through standardization

Native MQTT integration into InfluxDB Cloud allows for an open and standardized exchange of information. In simple terms, data brokers can integrate with InfluxDB as long as they comply with MQTT version 3.1.1. Forcing compliance eliminates the interoperability barrier often introduced when using third-party or proprietary orchestration tools for connecting to the time series database.

4. Reduced cost

Introducing customisation services between your MQTT broker and InfluxDB Cloud database increases the cost of your IoT system implementation and maintenance. There are several reasons for this. For instance, these services require costly physical infrastructure and highly skilled engineering talent to set up and keep them running indefinitely.

5. Scalable IoT solution

Having all components of an IoT system connected to one central location makes it highly scalable. That means your system’s performance and availability remains unchanged and predictable even as you add more components well into the millions. On the contrary, systems with intermediary services between IoT components and the MQTT broker do not retain reliability or predictability as they grow.

6. Ensures data integrity

In IoT Solutions, where there are multiple hops before data lands on a database, the data is usually re-formatted and, in some cases, aggregated along the way. This process causes data to lose its integrity.

On the other hand, if you have a direct connection between your time series database and a data medium that doesn’t alter data in any way, such as an MQTT broker, then you are guaranteed that your data is the same as when it left the source. Some solutions require such certainty for business process integration of IoT systems.

7. Consistent data parsing

While still on the topic that relates to data formatting, systems handle typecasting and data formatting differently. Therefore, it is a good idea to perform data formatting natively before persisting the data on the time series database.

InfluxDB-Cloud-Native-Collector

InfluxDB Cloud Native Collectors’ user interface to define data parsing rules

8. A bonus benefit – improved visibility

Here’s an additional bonus benefit! In an IoT solution where data goes through intermediary platforms, it is usually challenging to identify the source of a problem along the chain when something goes wrong. Eliminating intermediary services between your MQTT broker and database helps improve visibility when monitoring or troubleshooting your IoT system.

Conclusion

In conclusion, Native MQTT Integration into InfluxDB Cloud allows developers to focus on building and scaling IoT applications without worrying about additional software or new code. Taking this stress off your engineering team dramatically simplifies the development and maintenance of IoT solutions.

If you’d like to learn how to use Native MQTT Integration on InfluxDB Cloud to collect data directly from HiveMQ MQTT broker, then check out this detailed how-to guide.

About the author

Kudzai-Manditereza

Kudzai Manditereza is a Developer Advocate at HiveMQ and the Founder of Industry40.tv. He is the host of an IIoT Podcast and is involved in Industry 4.0 research and educational efforts.

You can contact him here [email protected] and find his profile here https://www.linkedin.com/in/kudzaimanditereza/