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
Conferences
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

Automating service delivery

The goal of service delivery is to reduce the number of steps required to deliver a service. This is true in IT as well as in edge computing. Whether it is a simple application or a machine learning (ML) model to be deployed on edge devices quickly and securely, automating those steps is what teams strive for. Doing so helps eliminate configuration errors and scale such solutions.

Physical installation of devices is not something that the OT can automate, but the configuration of the devices and deployment of applications that run on those devices can be automated. If a large bank that has over 10,000 ATMs across the country wants to apply an update to its ATMs, it cannot afford to send personnel to every ATM. Rather, the update is done remotely either through command-line scripts or a DevOps toolchain. Another good example is damage detection sensors on wind turbine blades monitored by edge nodes located on top of the wind turbines.

DevOps

Collaboration...

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