Our clients want telemetry data from our buildings via MQTT. We have 10+ buildings and 100,000~ data points. We will double in size in 5 years. Our devices can publish MQTT. I would like to aggregate data with HiveMQ and filter data for clients based on devices that monitor their inventory using a plugin. Each device has 5-10 data points. I’ve seen examples where 1.) a topic is used for each data point and 2.) all data points are part of a single topic in a JSON format. In either option I can filter on content/Topic to reroute data to the correct client. Which is considered the best practice a topic per data point or a topic per device based on the current/future number of devices? Are there other things to consider? Has someone published a paper on this?
Related Topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Using hivemq cloud - topics are removed from time to time | 1 | 270 | August 14, 2023 | |
|
How to create topics?Is topic is creating from ui side?
|
3 | 452 | August 10, 2023 | |
| How can I management my devices? | 2 | 431 | September 28, 2022 | |
| How can I build my topics if I have multiple machines and users? | 5 | 582 | May 29, 2022 | |
| How many topic can the HiveMQ CE create? | 1 | 1195 | November 11, 2019 |