29.07.2020, 21:45
(This post was last modified: 30.07.2020, 13:25 by Erwin van der Zwart.)
Hi,
There isn’t a lot to document..
The broker can be enabled, set a port and set users with password and optional encryption.
A client can subscribe to a topic to host or get data and another client or multiple clients can also subscribe to a topic hosted by the broker.
The broker is nothing more then the man in the middle with some retention, that’s it.. Clients are actually the ones that do the work, so if system A subscribes to a certian topic it let the broker know the topic exists, when system B wants this info then it connects to the broker and subscribes to that topic and the broker tells system B where to get the data.
There is some nice info on this website explaining MQTT
https://www.hivemq.com/tags/mqtt-essentials/
Check part 3 for more information about a MQTT Broker
BR,
Erwin
There isn’t a lot to document..
The broker can be enabled, set a port and set users with password and optional encryption.
A client can subscribe to a topic to host or get data and another client or multiple clients can also subscribe to a topic hosted by the broker.
The broker is nothing more then the man in the middle with some retention, that’s it.. Clients are actually the ones that do the work, so if system A subscribes to a certian topic it let the broker know the topic exists, when system B wants this info then it connects to the broker and subscribes to that topic and the broker tells system B where to get the data.
There is some nice info on this website explaining MQTT
https://www.hivemq.com/tags/mqtt-essentials/
Check part 3 for more information about a MQTT Broker
BR,
Erwin