The next step in adding message queuing without heavy infrastructures, server applications or licenses.
As you will need to use a data protocol when you want to connect your Internet of Things device to any network, there is a big chance "HTTP" will pop up as it is pretty standard. But in fact that will involve quite some coding, especially when you want 2- way communication.
Think of it, do you really want to implement an http/webserver on the smallest devices? Do you really want to do polling on devices that need to work in an energy efficient way? And how do you communicate a message to thousands of devices or vice versa?
And yes, we did take into account that your application is special. But the truth is that probably your special case has been solved already a thousand times before.
Next to that, you probably don't know today in what ways your device and the data from/to your device will be used in the future. Can you make sure the communication in your device is future proof?
And instead of burning precious project dollars, risking your time-to-market and maybe having to fix a lot of communications bugs, why don't you choose a reliable tested communication and have communication in place on day 1?
The answer to all these questions is simple: ZeroMQ. Time-to-market ensured!
ZeroMQ enables you to do so. It adds message queuing without any heavy infrastructures, server applications or licences. Also the messages contain very, very little framing overhead.
ZeroMQ supports over 50 different language bindings so you can start communicating with your devices in whatever programming language you like. Just 10 lines of code or less are enough to have full fledged, reliable message queuing. It will prepare your Internet of Things device for whatever kind of business integration you had in mind. And even for those you did not think of yet.
Just imagine what this will do to your "time-to-market" planning. But we have to give credit when credit is due. We did not invent ZeroMQ, it was already there. But we found it, tried it in combination with our TCP/IP stack, and fell in love with its possibilities and sheer simplicity.