Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Please lobby the IoT Hub team so we could run AF over websockets

See original GitHub issue

The whole point of Azure Functions is to take away the worry about infrastructure and provisioning of servers. However, as we live in 2017 it’s fundamentally important that we are able to talk to Azure Functions over websockets.

Azure IoT Hub is a broker that supports MQTT over WebSockets. Azure Functions on the other hand supports both IoT Hub triggers and outputs. This means we could run clients that talk to Azure Functions over WebSockets (using mqtt.js or pahojs for example) by relying on IoT Hub triggers and outputs.

Unfortunately, the above can not be accomplished not only because IoT Hub does not support CORS but also because CORS support seems to be a low priority for the IoT Hub team. This is surprising considering the fact that AWS IoT has supported CORS/WebSockets since January last year.

Most importantly, this prevents Azure Functions from fulfilling it’s “serverless” promise because right now the only way to talk WebSockets to Azure Functions is by running a cluster of servers for the sole purpose of brokering websocket <> http/iot connections.

We need someone from the Azure Functions team to physically head over to the IoT Hub team and explain to them that there’s a whole world outside Arduino that could use CORS support.

😉