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

Let the cat out of the bag (Successfully open source your code and documentation)

In this section, we’ll discuss different methods and approaches to open sourcing your materials, from the bare minimum to standard and formal approaches. By the end, you should have a good idea of your options and the benefits of each one.

Each of the options listed in this section share some common assumptions. Chief among those assumptions is that each repository should explicitly call out (meaning, draw attention to or otherwise direct the reader to) the main or default license. Do not make code available publicly without specifying a software license. Other assumptions are that each repository lists the maintainers, contributors, security reporting process, ways to contribute, and adopters. Finally, each repository should contain a README file (meaning, a file literally named “README” that contains information that should be consulted first) and a pointer to any other documentation...