Testing AMQP Protocol on Unstable and Mobile Networks

Abstract

However, implementations of this protocol have not been well tested in the context of mobile or unstable networks. This paper is the starting point of an experimental evaluation of AMQP protocol in such kind of scenarios. Our goal is to identify the limits of applicability of this middleware, assessing its the capacity in terms of message losses, latencies or jitter, when wireless devices are interrupted and reconnected. This evaluation is of interest for the upcoming applications in which personal devices and vehicles will collaborate, forming part of large complex systems.

Choice of effective messaging protocols for IoT systems: MQTT, CoAP, AMQP and HTTP

“…This reduces the overall overhead considerably, and thus the whole message size. AMQP is also a lightweight binary protocol; however, its support for security, reliability, provisioning and interoperability increases the overhead and message size [14], [19]. Finally, HTTP among all four is the most verbose and heavyweight protocol [17].…”

“…Various experimental studies found that CoAP consumes slightly less power and resources in similar circumstances: unreliable scenario (MQTT QoS 0 vs. CoAP NON), and reliable scenario (MQTT QoS 1 or 2 vs. CoAP CON), while assuming that no packet losses are happened [7], [8], [9], [17], [18]. AMQP requires slightly higher power and resources due to performing other necessary operations for provisioning and reliability [14], [19]. Finally, HTTP is a bigger than all and needs greater processing power [17], [20].…”

Impact of mobility on Message Oriented Middleware (MOM) protocols for collaboration in transportation

“…A schema of this approach is shown in Figure 2. Due to the asynchrony among the internal clocks of the different entities of a distributed system we cannot obtain an accurate latency value [7]. Instead, we have calculated the variation in the delay of the received messages, i.e., the jitter.…”

Application-derived communication protocol selection in M2M platforms for smart cities

“…Usually it happens when the server node was restarted. In AMQP, the messages are self-contained and data content in a message is opaque and immutable [98]. According to the specications, there is no limits for the message's size, it can either support a message of 1 GByte or just few bytes in size.…”