Why MQTT is better than REST
bevywise.com
bevywise.com
Not only does it works well for iot, but it also is very nice for the web and micro-service oriented architectures.
It's based on websocket, so it kinda works out of the box on most networks without bugging your local sysadmin, and has a bonus benefit of TLS support. And it's open standard with lots of open source clients, like MQTT.
It's also higher level, so you get (routed) RPC and PUB/SUB, with transparent result and error propagation accross language (you JS code in the browser can call you Java code on android discussing with your C# code in the cloud and your python code on the raspi).
The main implementation for the router, crossbar.io, works very well, with plenty of knobs for introspection, security, performance, etc. And you get authentication backed in.
No really, MQTT is very low level to my taste compared to WAMP.
Do check the medium link of the post -
https://medium.com/bevywise/mqtt-vs-rest-from-iot-implementa...
Does MQTT have any sort of future? I played with it about six months ago and it felt like a half-baked thing with no momentum.
All major providers of Platform supports MQTT and MQTT is going to be most widely used. Most of the current implementations are over REST which will not scale up as the frequency goes up.
interested to know what is the protocol you use today.