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

Non-functional requirements

Edge computing architectures must satisfy several NFRs. While low latency and high bandwidth are two of the most common and obvious requirements, enterprises often list security as their most important requirement. The other NFRs are related to service management and operations.

Security

When discussing inferencing, we mentioned that one of the outcomes of real-time inferencing at the source of the data is a better security posture since data doesn’t have to travel far, thus reducing the attack area. That said, any and all data in transit must be sent using a secure protocol. Onboarded devices could use keys, security certificates, or both. As in all IT solutions, components in an edge solution more often than not must meet regulatory, compliance, and local security standards because they deal with data. For a discussion of this topic in depth, see Chapter 6, where we cover security aspects of data in motion and data at rest.

Service management...