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

A software bill of materials is your friend

In this section, we will explore OSS supply chain issues – how to consume or depend on OSS without introducing new vulnerabilities using a Software Bill of Materials (SBOM), how to identify mature and stable OSS projects, how to nurture and assist projects you rely on, and responding to projects that abandon their initial commitments.

Using SBOMs to track software dependencies

A software architect can be called on to provide specific recommendations for OSS solutions in an architecture or implementation. The risks in doing so are that the proper solution (or one of its immediate dependencies) for a given set of requirements might be from a project that is not mature or stable (see the following subsection for more about that topic). Therefore, it is incumbent on you to perform due diligence, either recommending against using those projects or only with strong caveats when no other good options are available, so that the ultimate...