Explore chapters and articles related to this topic
Internet of Things-Compliant Platforms for Inter-Networking Metamaterials
Published in Christos Liaskos, The Internet of Materials, 2020
RabbitMQ[10] is an open-source message-broker software that originally implemented the Advanced Message Queuing Protocol (AMQP) and has since been extended with a plug-in architecture to support Streaming Text Oriented Messaging Protocol (STOMP), MQ Telemetry Transport (MQTT), and other protocols. The RabbitMQ server program is written in the Erlang programming language and is built on the Open Telecom Platform framework for clustering and failover. Client libraries to interface with the broker are available for all major programming languages. RabbitMQ has TLS and clustering support.
The Smart Grid IoT
Published in Stuart Borlase, Smart Grids, 2018
Stuart Borlase, Donivon D. Hettich, David Kranzler
The AMQP is an open standard for message-oriented middleware. It predominantly focuses on message queuing, routing, and orientation. It has publish/subscribe capabilities but is a binary layer protocol to support many messaging applications atop it. Like MQTT, AMQP is a connection-oriented protocol and relies on TCP/IP to help provide the message exchange reliability. Therefore, network bandwidth, latency, and microcontroller memory footprint and processing power may be more demanding than some other lightweight protocols.
Asynchronous Messaging
Published in Kevin E. Foltz, William R. Simpson, Enterprise Level Security 2, 2020
Kevin E. Foltz, William R. Simpson
AMQP is an open standard application layer protocol for message-oriented middleware [2].m). It is an emerging technology addressing the standardization problem. Implementations are interoperable. It includes flexible routing and common message paradigms like publish-subscribe, point-to-point, request-response, and fan-out.
Cyber-Physical Systems: a multi-criteria assessment for Internet-of-Things (IoT) systems
Published in Enterprise Information Systems, 2021
Edgar M. Silva, Ricardo Jardim-Goncalves
Data exchange protocol is another area related to communication. Data elements are exchanged to trigger a certain procedure or just to transfer data. Messages between nodes/components are based on mechanisms often called Message-Oriented Middleware (MOM), a specific software class used in distributed environments (Luzuriaga et al. 2015). Well-known standard examples are: Advanced Message Queuing Protocol (AMQP) a binary protocol with service semantics to achieve interoperability among entities (O’Hara 2007); Message Queuing Telemetry Transport (MQTT) (Banks and Gupta 2014), similar to AMQT, is a standard supported by the OASIS organisation, built to be simple, open, lightweight and easy to implement a connection; and Constrained Application Protocol (CoAP) (Shelby, Hartke, and Bormann 2014), specified as RFC 7252 by IETF, presents capability to discover services and resources, focus on specific characteristics of constrained environments (nodes and networks). Regarding the connectivity space they address, CoAP is focussed on interdevice and device–gateway communication. AMQP focusses on gateway–cloud communication, while MQTT covers all scope, i.e. device–cloud communication.