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 detailed errors and mistakes that you might commonly encounter both in designing architectures and in working with existing deployed solutions. Some of the remedies we’ve reviewed may seem like common sense to you, but not to others.

We went over practices that were developed specifically for the edge-native environment: pulling versus pushing and their security implications, discussing application dependency management and resolution approaches, and deployment models. The next section covered ways to think about designing antifragile solutions that improve when placed under stress instead of breaking when exposed to random events. In the last section, we went over our options when systems fail.

As a result, you should have a list of considerations that will help you to architect long-lived and resilient solutions for edge environments. We hope that you will not only put these recommendations and guidelines into practice but also pass along...