3 ms·

Thanks for the post! It was really a good read. In a similar position I would have tried MQTT that should handle quite well a great number of topics. Did you

by siscia 8y ago

Thanks for the post! It was really a good read. In a similar position I would have tried MQTT that should handle quite well a great number of topics. Did you guys tried such protocol?

achille-roussel 8y ago
Correct me if I’m wrong, but MQTT is just a network protocol, it doesn’t solve storage, retries, failure resilience, etc... it’s well suited for pub/sub operations over TCP, not so much for ensuring “exactly once” delivery of messages.
- Jakob 8y ago
  Most MQTT implementations support "exactly once delivery": https://en.wikipedia.org/wiki/Comparison_of_MQTT_Implementations#Quality_of_Service_(QoS)_levels_offered https://en.wikipedia.org/wiki/Comparison_of_MQTT_Implementat...
- siscia 8y ago
  Yes, you are correct. MQTT is a network protocol. You build your infrastructure on top of it to support stuff like storage, retries, resiliency, etc... However, it does gives you some guarantee, namely that the message will oblige its QoS (at most once, at least once, exactly once). On top of these guarantees, you build whatever you need. Honestly, I am quite glad that you are writing these posts, it is a great service for the community and if you end up open sourcing it, the project will bring a lot of value to everybody. Thanks for your posts :)