Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Edge Computing Patterns for Solution Architects

You're reading from   Edge Computing Patterns for Solution Architects Learn methods and principles of resilient distributed application architectures from hybrid cloud to far edge

Arrow left icon
Product type Paperback
Published in Jan 2024
Publisher Packt
ISBN-13 9781805124061
Length 214 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Ashok Iyengar Ashok Iyengar
Author Profile Icon Ashok Iyengar
Ashok Iyengar
Joseph Pearson Joseph Pearson
Author Profile Icon Joseph Pearson
Joseph Pearson
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Part 1:Overview of Edge Computing as a Problem Space FREE CHAPTER
2. Chapter 1: Our View of Edge Computing 3. Chapter 2: Edge Architectural Components 4. Part 2: Solution Architecture Archetypes in Context
5. Chapter 3: Core Edge Architecture 6. Chapter 4: Network Edge Architecture 7. Chapter 5: End-to-End Edge Architecture 8. Part 3: Related Considerations and Concluding Thoughts
9. Chapter 6: Data Has Weight and Inertia 10. Chapter 7: Automate to Achieve Scale 11. Chapter 8: Monitoring and Observability 12. Chapter 9: Connect Judiciously but Thoughtlessly 13. Chapter 10: Open Source Software Can Benefit You 14. Chapter 11: Recommendations and Best Practices 15. Index 16. Other Books You May Enjoy

Disconnected operations

In this section, we will cover unique options and opportunities for not only planning for interrupted network connections but actively planning for those scenarios as an operating requirement. You will learn how some organizations anticipate and respond to those situations in three separate approaches.

In the Delving into edge-in architectures section of Chapter 1, the first practice listed was Tolerate interruptions and unavailability of service dependencies and connectivity. In the edge device hub pattern, you should expect that each individual connection might be unavailable and plan for that eventuality. That may mean planning for devices to lose connectivity to their hub and for performance fluctuations. If that happens, do you plan for the devices to buffer enough untransmitted data, accept the potential data loss, or take some other approach? That may mean that the hub cannot provide the data in response to remote queries or cannot re-transmit the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image