Please enable JavaScript.
Coggle requires JavaScript to display documents.
MQTT (Message Queing Telemetry Transport), questions, capture_1, capture_2…
MQTT (Message Queing Telemetry Transport)
Concepts
Concepts - Publish & Subscribe, Messages, Topics, and then the Broker
MQTT was devloped by Andy Standford Clark of IBM and Arlen Nipper in 1999 for the monitoring of a oil pipeline through the desert
The goals were to have a protocol, which is bandwidth-effcient and uses little battery power, because devices were connected via satellite link and this was extremely expesnive at the time
MQTT is a publish-subscribe based lightweight protocol or over other network protocols that provide order, lossless, bidirectional connections
Is it designed for connections with remote locations where a small code-footprint is required or network bandwidth is limited
The publish-subscribe messaging pattern required a message broker
Broker is responsible for distributing messages to interested clients based on the topic of a message
A light-weight and messages oriented protocol, allowing devices to asynchronously communicate across restrained networks to remote systems with low bandwidth
Generic Publish-Subscribe Design Pattern
Methods Used
Connect, Disconnect, Subscribe, Unsubscribe, Publish
questions
fallacies distributed systems
grpc vs mqtt
mqtt publisher / subscriber
therorictial on rest services
