August 26th, 2011 - 2 Comments
A couple of weeks ago it was announced that plans were being put in place to move the MQTT protocol forward for standardization, along with a call for participants to that process.
As part of that change, a number of things have been added “behind the scenes” on mqtt.org, including a new Get Involved page listing the different places where conversations happen – including a new MQTT discussion group that will be properly launched shortly. There’s also a new Twitter ID, @mqttorg, where site updates and other news is being posted.
The site design has been freshened slightly (including a nicer mobile interface), and the upper menu will be reorganized soon to make sure that the Get Involved community page is visible. Expect more use to be made of the wiki in future, too. There has been a huge growth in interest in the use of the protocol over the past few weeks, and it would be great if more people could share their experiences on the wiki and in the different discussion areas. Remember to let us know if you are doing anything cool with MQTT – tag your tweets #mqtt to make sure you get our attention!
One final piece of news… if you are in the UK and interested in learning more about MQTT then you should check out the free 1-day messaging PubSub Huddle on September 23rd, where MQTT will be one of the technologies being discussed.
August 12th, 2011 - 4 Comments
This one has come slightly out of the blue. We’ve always known around here that MQTT is ideal for mobile messaging; the small-footprint, low bandwidth nature of the protocol helps to minimise both battery use and network traffic. Just what you want to stay connected.
Lucy Zhang, a software engineer at Facebook, has written about their new Facebook Messenger app:
One of the problems we experienced was long latency when sending a message. The method we were using to send was reliable but slow, and there were limitations on how much we could improve it. With just a few weeks until launch, we ended up building a new mechanism that maintains a persistent connection to our servers. To do this without killing battery life, we used a protocol called MQTT that we had experimented with in Beluga. MQTT is specifically designed for applications like sending telemetry data to and from space probes, so it is designed to use bandwidth and batteries sparingly. By maintaining an MQTT connection and routing messages through our chat pipeline, we were able to often achieve phone-to-phone delivery in the hundreds of milliseconds, rather than multiple seconds.
You can read her full post here.
[edit: of course, MQTT has also been used to build a Facebook “presence” device before, by our friends at Isidorey, but this new deployment inside Facebook is obviously something with much broader reach!]
August 12th, 2011 - 7 Comments
MQTT has been around for over 10 years. It has seen many successful, wide-scale implementations in that time, too. Until now, the protocol specification has been shared between IBM and Eurotech, although it is published under royalty-free terms for ease of use, understanding and implementation.
Today, we’re delighted to announce that the specification will be moved toward formal standardization. Since so many groups, communities, and individual developers have expressed an interest, we’re also very excited to make this process open for anyone to join:
The MQTT protocol specification, in the public domain since 1999, was published under royalty free terms in 2010. New M2M solutions, fuelled by exponential growth in wireless device connections, bring the need for reliable and scalable messaging. To support industry growth and ensure open connectivity, Eurotech and IBM are planning to bring the MQTT protocol to a standards organization. We welcome your interest and participation in this standardization initiative.
You can download the full announcement (PDF), which includes details of who to contact in order to get involved.