Search icon CANCEL
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
IoT and Edge Computing for Architects

You're reading from   IoT and Edge Computing for Architects Implementing edge and IoT systems from sensors to clouds with communication systems, analytics, and security

Arrow left icon
Product type Paperback
Published in Mar 2020
Publisher Packt
ISBN-13 9781839214806
Length 632 pages
Edition 2nd Edition
Arrow right icon
Author (1):
Arrow left icon
Perry Lea Perry Lea
Author Profile Icon Perry Lea
Perry Lea
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. IoT and Edge Computing Definition and Use Cases 2. IoT Architecture and Core IoT Modules FREE CHAPTER 3. Sensors, Endpoints, and Power Systems 4. Communications and Information Theory 5. Non-IP Based WPAN 6. IP-Based WPAN and WLAN 7. Long-Range Communication Systems and Protocols (WAN) 8. Edge Computing 9. Edge Routing and Networking 10. Edge to Cloud Protocols 11. Cloud and Fog Topologies 12. Data Analytics and Machine Learning in the Cloud and Edge 13. IoT and Edge Security 14. Consortiums and Communities 15. Other Books You May Enjoy
16. Index

Sensors, Endpoints, and Power Systems

The Internet of Things (IoT) begins with sources of data or devices that perform an action. These we call endpoints or nodes, and they are the things associated with the Internet. When one discusses IoT, in general, the actual sources of data are often overlooked. These sources are sensors outputting a stream of time-correlated data that must be transmitted securely, possibly analyzed, and possibly stored. The value of IoT is in the data in aggregate. Therefore, the data a sensor provides is crucial. However, for an architect, it is critical to understand the data as well as how the data is interpreted. Besides understanding what data is collected and how it is acquired, in a massive IoT deployment, it is useful to know what can be sensed, and what the constraints are for various sensors. For example, a system must account for lost devices and erroneous data. An architect must understand the reasons...

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