3

I have an architecture where many sensors (hundreds of them), located in different places (hundreds of kilometers apart), send data to a remote database. Is MQTT suitable for this kind of configurations?.

I was thinking in installing the MQTT broker and my backend in the same server and make the backend subscribe to one topic where all the sensors would be writing. So there would not be any communication between sensor nodes; the communication will be only between each sensor node and the server.

Also, the sensor nodes would be gruped by client (maybe 10 nodes in the same place).

  • 1
    What makes you think it wouldn't work? – hardillb Apr 16 at 16:43
  • go here to help you visualize how MQTT works and how to use it ... shiftr.io/try ... it is pretty cool – jsotola Apr 16 at 17:39
  • I was worried about the amount of data that would be redirected to only one node – Gaspar S. Apr 16 at 18:30
2

This sort of thing is perfect for MQTT.

You also don't need to have all the sensors publishing on the same topic, they could all publish to the same topic prefix and the processing app can use a wildcard subscription to have all the messages delivered. Or you can have multiple backend processing apps that split the load by subscribing to different wildecards.

e.g. a topic made up like

 country/region/city/sensor-id

You could then have different processing apps subscribe to

England/#
Scotland/#
USA/Florida/#
USA/California/SanFransico/#
| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.