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

Summary

In this chapter, we discussed the main components of an edge architecture. You learned that what makes edge architecture rather unique is the inclusion and heterogeneity of the plethora of edge devices. The typical functional requirements are few, but they are relevant and can be applied to various use cases across a whole lot of industries. We also discussed the different NFRs and their scope.

Lastly, there are many design decisions that solution architects have to make that could be overwhelming. Some of the common ADs were provided more as a starter set. We alluded to the complexity of architecting an edge solution because there are software and hardware components to account for, especially in edge-native designs. This should get architects thinking of the different aspects and domains. In the next three chapters, we will dive into the various architectures from basic to complex and provide recommended practices.