Main Site Documentation

Microsoft Azure Intelligent Systems Service Limited Public Preview


#1

Sign up here :slight_smile:

https://connect.microsoft.com/site1132/Survey/Survey.aspx?SurveyID=16303


#2

Heck ya I signed up for that, hopefully I get in.

Wonder if Azure will ever offer a MQTT option or something like it.


#3

M2Mqtt : MQTT client library for Internet of Things & M2M communication

http://code.msdn.microsoft.com/windowsdesktop/M2Mqtt-MQTT-client-library-ac6d3858#content


#4

@ RomanMiler I did a demo project and video etc on M2Mqtt here https://www.ghielectronics.com/community/codeshare/entry/896

@ Paolo (the guy behind M2Mqtt is a community forum member here.


#5

@ DukeNukem Great video !


#6

Yes:
"If MQTT remains your choice, I will try to make you as successful with it as I can…There were times when technical pride would get in the way of folks working at Microsoft supporting what the customers demand; that’s not my notion of running “services”. "

In spite of:
“MQTT is an old, recycled, and often weirdly inconsistent mess. It’s not a good protocol, and certainly not a good protocol for the Internet of Things”

See here for a detailed technical discussion:


#7

Some Information about MQTT and Azure

https://mqttbroker.codeplex.com/

http://www.embedded101.com/Blogs/PaoloPatierno/tabid/106/entryid/455/GnatMQ-in-the-Cloud-an-MQTT-broker-on-Microsoft-Azure.aspx

@ Cuno

You know a good alternative???

Whats about AMQP, COAP?

http://www.amqp.org/

http://www.coapsharp.com/


#8

Depends on the project, but if plain HTTP is not applicable for some reason, I’d next take a look at CoAP. It can be regarded as a compressed form of HTTP (therefore a trivial mapping from and to HTTP exists) plus a few additional features like subscription to sensor data (Observe option). Lightweight enough to be implemented on 8-bit microcontrollers. Although if you need TLS for security, the bandwidth difference to HTTP may not be that large anymore (same holds for MQTT and AMQP)…

A more long-term alternative could be Bluetooth Low Energy’s GATT protocol. As an application layer protocol over any transport, not just BLE. Like HTTP and CoAP basically a RESTful design, with a defined mapping from and to HTTP. The current key exchange mechanism is weak however, a more secure one is under discussion.

I’d also consider 0MQ (ZeroMQ). ZeroMQ is light-weight, including security. It basically uses the same algorithms that we have experimentally implemented in our [em]Oberon.NaCl[/em] library (http://www.mountaineer.org/resources/tidbits/using-the-nacl-crypto-library/).

But first I’d try to stick with HTTP and see how far I’d get with that.

Cuno

PS
AMQP may be too heavy for small embedded devices, in particular if you need SSL in addition. But as Microsoft appears to be pushing AMQP, it might become an alternative if and when someone provides a light-weight SSL implementation for NETMF. See also


#9

When I did my MQTT sample project on Gadgeteer ( https://www.ghielectronics.com/community/codeshare/entry/896 ), I then tried to do a AMQP sample based on the same hardware setup and objective (controlling some leds), and found AMQP rather daunting so unless AMQP does some more work I would tend to agree that it might not be suitable for small devices, but I see IoT as having a lot of small devices so use of AMQP could be limited in IoT.


#10

Me too. And I don’t count G120 (or anything with external RAM and/or flash) as a “small device”. Cerb40 barely qualifies, in my book.