FarmMaps/Documentatie
8
0
Fork 0
Code Pull Requests Releases Activity

Update page 'Message Queue Endpoint'

Browse Source
This commit is contained in:
Auke Sytsma 2020-03-01 10:36:40 +00:00
parent b0f72eea97
commit 8a89be8b1a
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Message-Queue-Endpoint.md
View File

@ -41,7 +41,8 @@ Generally, one user is provided per application (so no individual users for diff
### Settings
To connect to the MQTT Broker, we'll use the following settings:
**MQTT connection settings**
**MQTT connection settings**
| Parameter | Default | Description |
| :---: | :------------------------------------------: | --- |
| CLIENT_ID | - | This ID is used to identify the connecting party (your software) to the broker, please use your company or brand name. |
@ -68,7 +69,7 @@ All settings are required except for the `META_DATA_URL`, this parameter is opti
### FAQ
#### What is a message queue? (skip ahead if familiar)
#### What is a message queue?
A message queue is commonly used to make software programs able to send messages between eachother, and thereby making it easy for data to flow from one program into another. There are many variants of message queues, some popular names are Apache Kafka, MQTT and RabbitMQ.
In message queue systems there is usually one central "hub" called the broker or **"message broker"**. This broker holds all the messages. Usually, the messages are organised in groups called **"topics"**.