simplifying the description by removing unneeded info

* Showing the users that they can register to only a subset topics promotes bad practices when other topic schemas are used. * Removed the comment about the centralized database as this feels too negative and goes outside of the scope of the reference doc Signed-off-by: Reuben Miller <[email protected]>
thin-edge · Jul 14, 2023 · 5c56ea9 · 5c56ea9
1 parent 51bae82
commit 5c56ea9
Showing 1 changed file with 1 addition and 12 deletions.
diff --git a/docs/src/references/mqtt-api.md b/docs/src/references/mqtt-api.md
@@ -403,19 +403,8 @@ for all possible entity identification topic levels as follows:
 mosquitto_sub -t 'te/+' -t 'te/+/+' -t 'te/+/+/+' -t 'te/+/+/+/+'
 ```
 
-If your use-case has a fixed schema, something like `te/<device-namespace>/<device-id>/<service-namespace>/<service-id>/...`
-then you could limit to your subscriptions to a specific set of topics where you expect the registrations as follows:
-
-```sh
-mosquitto_sub -t 'te/+/+' -t 'te/+/+/+/+'
-```
-
-Where the subscription is limited to just devices at level 3 and services at level 5.
-
 :::note
-Thin Edge does not maintain a centralized database of these entities that other components can query.
-Instead, the MQTT broker is used to store all the info about entities as retained messages
-and components are free to build their own internal entity store from these retained messages with just the relevant data.
+The MQTT broker is used as the persistance layer to store the registered entities (assuming the registration messages were published with the MQTT retain flag).
 :::
 
 ## Data types