Book Image

Internet of Things for Architects

By : Perry Lea
Book Image

Internet of Things for Architects

By: Perry Lea

Overview of this book

The Internet of Things (IoT) is the fastest growing technology market. Industries are embracing IoT technologies to improve operational expenses, product life, and people's well-being. An architectural guide is necessary if you want to traverse the spectrum of technologies needed to build a successful IoT system, whether that's a single device or millions of devices. This book encompasses the entire spectrum of IoT solutions, from sensors to the cloud. We start by examining modern sensor systems and focus on their power and functionality. After that, we dive deep into communication theory, paying close attention to near-range PAN, including the new Bluetooth® 5.0 specification and mesh networks. Then, we explore IP-based communication in LAN and WAN, including 802.11ah, 5G LTE cellular, Sigfox, and LoRaWAN. Next, we cover edge routing and gateways and their role in fog computing, as well as the messaging protocols of MQTT and CoAP. With the data now in internet form, you'll get an understanding of cloud and fog architectures, including the OpenFog standards. We wrap up the analytics portion of the book with the application of statistical analysis, complex event processing, and deep learning models. Finally, we conclude by providing a holistic view of the IoT security stack and the anatomical details of IoT exploits while countering them with software defined perimeters and blockchains.
Table of Contents (18 chapters)
Title Page
Packt Upsell
Contributors
Preface
Free Chapter
1
The IoT Story

Other protocols


There are many other messaging protocols in use or proposed for IoT and M2M deployments. By far the most prevalent are MQTT and CoAP; the next sections explore a few alternatives for specific use cases.

STOMP

STOMP stands for Simple (or Streaming) Text Message-Oriented Middleware Protocol. It is a text-based protocol designed by Codehaus to operate with message-oriented middleware. A broker developed in one programming language can receive messages from a client written in another. The protocol has similarities to HTTP and operates over TCP. STOMP consists of a frame header and a frame body. The current specification is STOMP 1.2, dated October 22, 2012, and is available under a free license.

It is different from many protocols presented as it does not deal with subscription topics or queues. It simply uses HTTP-like semantics such as SEND with a destination string. A broker must dissect the message and map to a topic or queue for the client. A consumer of the data will SUBSCRIBE...