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
Internet of Things for Architects

You're reading from   Internet of Things for Architects Architecting IoT solutions by implementing sensors, communication infrastructure, edge computing, analytics, and security

Arrow left icon
Product type Paperback
Published in Jan 2018
Publisher Packt
ISBN-13 9781788470599
Length 524 pages
Edition 1st 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 (15) Chapters Close

Preface 1. The IoT Story FREE CHAPTER 2. IoT Architecture and Core IoT Modules 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. Routers and Gateways 9. IoT Edge to Cloud Protocols 10. Cloud and Fog Topologies 11. Data Analytics and Machine Learning in the Cloud and in the Fog 12. IoT Security 13. Consortiums and Communities 14. Other Books You May Enjoy

Other protocols


There are many other messaging protocols in use or proposed for IoT and M2M deployments. By far the most prevalent are MQTT and CoAP; the next sections explore a few alternatives for specific use cases.

STOMP

STOMP stands for Simple (or Streaming) Text Message-Oriented Middleware Protocol. It is a text-based protocol designed by Codehaus to operate with message-oriented middleware. A broker developed in one programming language can receive messages from a client written in another. The protocol has similarities to HTTP and operates over TCP. STOMP consists of a frame header and a frame body. The current specification is STOMP 1.2, dated October 22, 2012, and is available under a free license.

It is different from many protocols presented as it does not deal with subscription topics or queues. It simply uses HTTP-like semantics such as SEND with a destination string. A broker must dissect the message and map to a topic or queue for the client. A consumer of the data will SUBSCRIBE...

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 €18.99/month. Cancel anytime