Timeline for Is MQTT scalable with 1000+ clients?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 28, 2018 at 18:04 | comment | added | shal | As usual there are pros and cons of both options. It is obviously that any SaaS broker require perfect communicative team, long term testing on the early stage of the product development, clear uptime guarantees and various SLA. Maintaining own broker is also nice way, but the world is moving into services. Either you will put efforts and being most competent with your product that uses broker as part of it or you will spent you time and money on being super experienced MQTT-broker administrator (and never be its developer!). Just a matter of choice +) | |
| Feb 22, 2018 at 13:11 | comment | added | Dominik Obermaier | I don't think a SaaS MQTT broker is always the best for production. Most professional (self-hosted) MQTT brokers support HA, redundancy and failover at scale while maintaining full MQTT compatibility. Some SaaS brokers don't support all MQTT features. If you test against a local mosquitto and then go to a SaaS provider, chances are that things don't work in production as intended. | |
| Feb 19, 2018 at 3:43 | history | answered | shal | CC BY-SA 3.0 |