Every day millions of new devices are connected to the Internet. While desktops and laptops usually aren’t limited by network bandwidth or power, mobile devices need every bit of efficiency. Think about the power and bandwidth on a sensor installed on the oil pipe in Alaska, or a heart rate sensor, sensor in a car, etc. This is called IoT (Internet of Things). IoT is not just a marketing buzzword – it is very real (and useful).
When it comes to protocol choices, there are quite a few available, but there are many limitations and caveats for each of these. Some work only on LAN and can not go easily thru the firewalls, others have too much overhead for metadata, or support only a limited number of platforms or programming languages, etc.:
- SOAP (over other protocols)
Considering this wide variety of protocols available, which one is the best for the IoT? Check out this excellent presentation by Joe Speed on SlideShare where he discusses how many industries are now using MQTT to connect those sensors and devices to the Internet:
You may also want to read this technical article from IBM developerWorks “What is MQTT and how does it work with WebSphere MQ?“:“MQ Telemetry Transport (MQTT) is a lightweight network protocol used for publish/subscribe messaging between devices. The “MQ Integrator SCADA Device Protocol” is an old name for what is now known as MQTT. MQTT is designed to be open, simple and easy to implement, allowing thousands of lightweight clients to be supported by a single server. These characteristics make it ideal for use in constrained environments or low-bandwidth networks with limited processing capabilities, small memory capacities and high latency. The MQTT design minimizes network bandwidth requirements while attempting to ensure reliability of delivery…” Read the rest of the article.