Book Image

Edge Computing Patterns for Solution Architects

By : Ashok Iyengar, Joseph Pearson
Book Image

Edge Computing Patterns for Solution Architects

By: Ashok Iyengar, Joseph Pearson

Overview of this book

Enriched with insights from a hyperscaler’s perspective, Edge Computing Patterns for Solution Architects will prepare you for seamless collaboration with communication service providers (CSPs) and device manufacturers and help you in making the pivotal choice between cloud-out and edge-in approaches. This book presents industry-specific use cases that shape tailored edge solutions, addressing non-functional requirements to unlock the potential of standard edge components. As you progress, you’ll navigate the archetypes of edge solution architecture from the basics to network edge and end-to-end configurations. You’ll also discover the weight of data and the power of automation for scale and immerse yourself in the edge mantra of low latency and high bandwidth, absorbing invaluable do's and don'ts from real-world experiences. Recommended practices, honed through practical insights, have also been added to guide you in mastering the dynamic realm of edge computing. By the end of this book, you'll have built a comprehensive understanding of edge concepts and terminology and be ready to traverse the evolving edge computing landscape.
Table of Contents (17 chapters)
Free Chapter
1
Part 1:Overview of Edge Computing as a Problem Space
4
Part 2: Solution Architecture Archetypes in Context
8
Part 3: Related Considerations and Concluding Thoughts

Device configuration

In this section, we will cover the device configuration use case as an introduction to the edge device hub archetype pattern. You will learn the role and purpose of the infrastructure, platforms, and applications (collectively referred to as architectural elements going forward and shown in Figure 3.4) that support device operation at the edge. We will briefly discuss the benefits and drawbacks of placement decisions.

Rationale

The device configuration use case is meant to supplant legacy IoT architectures that connect fixed-function devices and embedded systems directly to a host in the cloud. Having a single platform for all devices puts the burden of device registration, protocol support, data collection, and analytics on one platform in one location. However, this approach required all data to be sent to the cloud if it wasn’t discarded, resulted in delayed analysis (thus delayed reaction times due to latency), and incurred data transfer and storage...