TY - GEN
T1 - MQTT Broker Performance Comparison between AWS, Microsoft Azure and Google Cloud Platform
AU - Suwardi Ansyah, Adi Surya
AU - Arifin, Miftahol
AU - Alfan, Muhammad Bahauddin
AU - Suriawan, Matthew Vieri
AU - Farhansyah, Nadhif Haikal
AU - Shiddiqi, Ary Mazharuddin
AU - Studiawan, Hudan
N1 - Publisher Copyright:
© 2023 IEEE.
PY - 2023
Y1 - 2023
N2 - 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.
AB - 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.
KW - AWS
KW - Azure
KW - GCP
KW - IoT
KW - MQTT Broker
KW - MQTTLoader
UR - https://www.scopus.com/pages/publications/85159491748
U2 - 10.1109/ICRTEC56977.2023.10111870
DO - 10.1109/ICRTEC56977.2023.10111870
M3 - Conference contribution
AN - SCOPUS:85159491748
T3 - ICRTEC 2023 - Proceedings: IEEE International Conference on Recent Trends in Electronics and Communication: Upcoming Technologies for Smart Systems
BT - ICRTEC 2023 - Proceedings
PB - Institute of Electrical and Electronics Engineers Inc.
T2 - 2023 IEEE International Conference on Recent Trends in Electronics and Communication, ICRTEC 2023
Y2 - 10 February 2023 through 11 February 2023
ER -