MQTT Broker Performance Comparison between AWS, Microsoft Azure and Google Cloud Platform

The rapid development of a new communication technology called the Internet of Things (IoT) has caused this technology to dominate the current technology market. The easy access of IoT to various devices has led to the development of new applications that generate several data from different objects...

Full description

Saved in:
Bibliographic Details
Published in2023 International Conference on Recent Trends in Electronics and Communication (ICRTEC) pp. 1 - 6
Main Authors Suwardi Ansyah, Adi Surya, Arifin, Miftahol, Alfan, Muhammad Bahauddin, Suriawan, Matthew Vieri, Farhansyah, Nadhif Haikal, Shiddiqi, Ary Mazharuddin, Studiawan, Hudan
Format Conference Proceeding
LanguageEnglish
Published IEEE 10.02.2023
Subjects
AWS
Azure
Bandwidth
Cloud computing
GCP
IoT
Machine-to-machine communications
MQTT Broker
MQTTLoader
Performance evaluation
Protocols
Quality of service
Throughput
Online AccessGet full text

Cover

More Information
Summary:The rapid development of a new communication technology called the Internet of Things (IoT) has caused this technology to dominate the current technology market. The easy access of IoT to various devices has led to the development of new applications that generate several data from different objects. In its implementation, IoT requires a protocol that has high communication performance, fast response and light size. MQTT is the right protocol for IoT because this protocol is designed for machine-to-machine communication and can send data quickly and with low bandwidth. MQTT consists of three main components, namely Publisher, Broker and Subscriber. Publishers are IoT devices that periodically send sensor data to data subscription applications known as Subscribers. While MQTT Broker is an entity that collects data sent by publishers and then forwards it to subscribers. In previous studies, many studies discussed the comparison of the performance of the HTTP Protocol in Cloud Services. This research discusses the performance of existing MQTT Brokers on AWS, Microsoft Azure and Google Cloud Platform (GCP) cloud services. It was found that Azure is good for using the Average Throughput Subscriber parameter at each QoS level and the Average Throughput Publisher at QoS 1 and 2. Meanwhile, GCP is good for using the Average throughput publisher at QoS level 0 and receives the most messages at QoS levels 1 and 2.
DOI:10.1109/ICRTEC56977.2023.10111870