Happy IoTFriday ! Today we are going to talk about three of the most popular Internet of Things protocols: HTTP, REST, MQTT and CoAP.
These three protocols are often discussed among experts who decide which one has the best features, security, and lowest cost, among several other important categories. Deciding which protocol should be used depends on your needs and potential uses. At thethings.iO, we have endpoints with REST, MQTT, CoAp and Websockets. (You can find documentation for IoT developers here.)
Marc showing 3 Internet of Things protocols #iotfriday
REST APIs are the most popular of the protocols. Based on HTTP and TCP/IP, it is the most standard used to share information among services on the Internet. REST APIs enable developers to access their data using market standardized methods and formats also known as JSON and XMLs.
MQTT (Message Queue Telemetry Transport) is an IBM open source protocol that offers a light-weight and easy publish-subscribe outlet to the Internet of Things. MQTT is based on TCP/IP in which several platforms are using for atomization of subscriptions and push messages to customers.
Lastly, CoAP (Constrained Application Protocol) is a simplification of the HTTP protocol. CoAp is mostly designed for processing restrictions that cannot process or run HTTP on the hardware. Even though it is not a standardized protocol, there are a lot of interesting features such as the observe or discovery methods that will boost the Internet of Things.
At thethings.iO, we are offering for developers four Internet of Things protocols. Write us in order to have an invitation and test our Internet of Things real-time platform.
Awake and welcome to the Programmable World @ Wired US June 2013
The author explains clearly the next three steps of the Internet of Things:
For the Programmable World to reach its full potential, we need to pass through three stages. The first is simply the act of getting more devices onto the network—more sensors, more processors in everyday objects, more wireless hookups to extract data from the processors that already exist. The second is to make those devices rely on one another, coordinating their actions to carry out simple tasks without any human intervention. The third and final stage, once connected things become ubiquitous, is to understand them as a system to be programmed, a bona fide platform that can run software in much the same manner that a computer or smartphone can. Once we get there, that system will transform the world of everyday objects into a designable environment, a playground for coders and engineers.
At theThings.IO we fully agree with this evolution of the Internet of Things, with some comments.
For the first step more evangelizers are needed. From my point of view, most of the manufacturers and OEMs are still dubitative about the Internet of Things. The history says that people is not really interested on objects with embedded gadgets, such as the “smart” fridge, the “smart” coffee machine, et al. We must move from the gadget connected to the Internet to the object with a real value. That said, the openness of these objects is needed.
For the second stage, I could say that years of research have been granted innovating on this topic. Brokers, hubs, ESBs, lightweight M2M protocols among other technical names have been developed in order to make the interoperability a reality. As Bill Wasik pointed, Smart Things is doing an amazing work on that field with their hardware. Ninja Blocks is also working on this direction.
The final stage is the most interesting. We are focused on developing to make real this third stage. We truly believe that developers might be able to apply their innovation and creativity on the top of the Internet connected objects. Manufacturers will be empowered with objects with new functionalities. And finally end-users with objects that can be reprogrammed for free or just for few cents.
We love this idea of hacking objects… why a glass cannot be a flowerpot?