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

Edge use cases and patterns

Edge use cases depend a lot on the industry that is targeted. So do the related applications that get deployed on the devices that generate or collect data. While the software stack might be similar, the form factor of the devices in play will determine the size and complexity of the applications. The applications will depend on the use cases relevant to a particular industry. For example, a camera might be trained differently when acting as a security camera than one looking for welding defects on a manufacturing shop floor. The devices are similar, in that they are both cameras, but the application or workload running on them is different depending on their function.

Edge workloads are often used to describe any edge-hosted service. Any software application that has utility when running in an edge node can be described as an edge workload. Such functionality is usually delivered as microservices running in Docker containers or related container technology...