"When you look at the wire trace of an HTTP packet, you end up with a lot of stuff in the headers which you don't see as a user," he tells RWW. "HTTP was designed for getting documents to a user interface. And it's been kind of bent and twisted into being used for inter-application and server-side communication, and that's fine when you have the bandwidth. But if you just want to send, 'The temperature is ___,' and then send 61.7, 60,7, 61.7, every five seconds, you really don't want to be doing a full HTTP post to send that information to an endpoint. So [MQTT] is asynchronous push; it's not request/response, which is what HTTP is."