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

Containers

In this section, we will cover the importance of using containers when developing applications and services. You will learn about how this innovation propelled edge computing to wide adoption. We will briefly discuss serverless computing (AKA cloud functions), and we will touch on the promise of Wasm and the Wasm System Interface (WASI) for edge computing.

As mentioned in Chapter 1’s Cloud-out versus edge-in section, software development for edge computing benefitted greatly from the best practices developed for the cloud environment. A large aspect of that benefit was the use of service-oriented (SO) software architectures, followed by containerization.

Containerized applications use principles of isolation and abstraction to remove some host and operating system dependencies from the packaged applications that need to run in those environments. This also allows applications with conflicting dependencies to run on the same host without contention. This abstraction...