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

Disconnected operations

In this section, we will cover unique options and opportunities for not only planning for interrupted network connections but actively planning for those scenarios as an operating requirement. You will learn how some organizations anticipate and respond to those situations in three separate approaches.

In the Delving into edge-in architectures section of Chapter 1, the first practice listed was Tolerate interruptions and unavailability of service dependencies and connectivity. In the edge device hub pattern, you should expect that each individual connection might be unavailable and plan for that eventuality. That may mean planning for devices to lose connectivity to their hub and for performance fluctuations. If that happens, do you plan for the devices to buffer enough untransmitted data, accept the potential data loss, or take some other approach? That may mean that the hub cannot provide the data in response to remote queries or cannot re-transmit the...