Slightly tangental, however I've been waiting for months for an Azure IoT thread to post this mini rant on... My team and I spent a few weeks working with Azur

Slightly tangental, however I've been waiting for months for an Azure IoT thread to post this mini rant on... My team and I spent a few weeks working with Azure IoT before instigating a switch to an alternative. The problem with Azure IoT as a platform is that they provide SDK documentation (which is relatively good for languages they like), but not API documentation for the AMQP interface which is their preferred method of connecting devices. Their support for python clients and servers (in particular servers) left me and my team spending circa 10 days digging through AMQP logs and wireshark in ever more desperate attempts to integrate our existing python server with Azure IoT. Eventually it became clear that our only option was to wrap the C library for a really brittle integration and that we could switch to a different platform with far less effort! Both Amazon IoT and Watson IoT have been far smoother to integrate with since they provide both SDK and API docs! The tough thing about it is that on the surface it looks as though it's really well documented and it's not until you hit your first big problem that you start looking around for API docs to try and debug what exactly it is that's wrong! Currently really fond of Watson IoT for the decent python SDK's (we've only got 2-3 patches in a fork!) and the really handy device management features which can make rebooting etc much easier from the server side. The MQTT implementation they've worked on is great too.