From 8a89be8b1ae236160a02df54b088d22cecc8e749 Mon Sep 17 00:00:00 2001 From: auke Date: Sun, 1 Mar 2020 10:36:40 +0000 Subject: [PATCH] Update page 'Message Queue Endpoint' --- Message-Queue-Endpoint.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Message-Queue-Endpoint.md b/Message-Queue-Endpoint.md index cc11708..2cf0327 100644 --- a/Message-Queue-Endpoint.md +++ b/Message-Queue-Endpoint.md @@ -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"**.