Book Image

IoT and Edge Computing for Architects - Second Edition

By : Perry Lea
Book Image

IoT and Edge Computing for Architects - Second Edition

By: Perry Lea

Overview of this book

Industries are embracing IoT technologies to improve operational expenses, product life, and people's well-being. An architectural guide is needed 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 IoT devices. IoT and Edge Computing for Architects, Second Edition encompasses the entire spectrum of IoT solutions, from IoT sensors to the cloud. It examines modern sensor systems, focusing on their power and functionality. It also looks at communication theory, paying close attention to near-range PAN, including the new Bluetooth® 5.0 specification and mesh networks. Then, the book explores IP-based communication in LAN and WAN, including 802.11ah, 5G LTE cellular, Sigfox, and LoRaWAN. It also explains edge computing, routing and gateways, and their role in fog computing, as well as the messaging protocols of MQTT 5.0 and CoAP. With the data now in internet form, you'll get an understanding of cloud and fog architectures, including the OpenFog standards. The book wraps up the analytics portion with the application of statistical analysis, complex event processing, and deep learning models. The book then concludes by providing a holistic view of IoT security, cryptography, and shell security in addition to software-defined perimeters and blockchains.
Table of Contents (17 chapters)
15
Other Books You May Enjoy
16
Index

Edge platforms

The software and applications running on the edge define its purpose. As you scale edge devices, managing them remotely becomes the challenge. Certainly, custom control and deployment models exist and are used in production. However, today, we have commercial off-the-shelf edge management frameworks as well as container-based methodologies that ease the burden of deploying software in a secure and controlled manner to remote edge computers.

In either case, we want the software and system to be:

  1. Robust: Capable of receiving, reimaging, and rerunning software as it is deployed
  2. Controlled: Having a central cloud or service that manages and monitors the deployment
  1. Responsive: Reporting back information on the success or failure of software reimaging

Virtualization

We can contrast the types of virtualization as follows:

Hardware virtualization: A hardware-level abstraction that is generally capable of running any...