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
Mastering Internet of Things

You're reading from   Mastering Internet of Things Design and create your own IoT applications using Raspberry Pi 3

Arrow left icon
Product type Paperback
Published in Mar 2018
Publisher Packt
ISBN-13 9781788397483
Length 410 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Peter Waher Peter Waher
Author Profile Icon Peter Waher
Peter Waher
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Preparing Our First Raspberry Pi Project 2. Creating a Sensor to Measure Ambient Light FREE CHAPTER 3. Creating an Actuator for Controlling Illumination 4. Publishing Information Using MQTT 5. Publishing Data Using HTTP 6. Creating Web Pages for Your Devices 7. Communicating More Efficiently Using CoAP 8. Interoperability 9. Social Interaction with Your Devices Using XMPP 10. The Controller 11. Product Life Cycle 12. Concentrators and Bridges 13. Using an Internet of Things Service Platform 14. IoT Harmonization 15. Security for the Internet of Things 16. Privacy 17. Other Books You May Enjoy

Getting to a better place


Regardless of whether you want it or not, if you're designing something for the Internet of Things, you must lay the foundation for it at the beginning. At the core of the foundation lies communication (among other things). Throughout the chapters, we've seen that protocols such as MQTT and HTTP, while they are easy to use, form a very bad foundation for interconnected things on the internet. While there are applications where they can be used, such as secondary web interfaces (HTTP) and local distributions of data (MQTT), for interoperability and exchange of data between devices on the internet, they are poor options. The amount of vulnerabilities you need to protect against, as well as the lack of communication pattern support, greatly outweighs using another protocol. CoAP with LWM2M might be a good choice, but only if the topology remains fixed, and if data collection and centralized processing is your main (or only) mode of communication. It's also a very poor...

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