Azure's IoT Lineup: Which Tools for Which Tasks?
For the emerging area of Internet of Things (IoT), developers face a confusing array of choices in a few different areas within Microsoft's catalog of Azure services.
To that end, Microsoft Azure MVP and Microsoft Regional Director Eric Boyd offered some guidance on a couple of key architectural questions this week, as part of a session at the Live! 360 conference in Orlando.
Boyd, the founder and CEO of responsiveX, has spent time the last few years experimenting with a burgeoning collection of IoT devices and components in his home and with the ways he can use Azure services to light up and connect the devices.
From watching his enthusiasm during a running demo throughout his presentation with a Raspberry Pi, you could tell he's been doing it partly because it's fun. The larger purpose has been getting to know the technology so well that he can help his clients figure out how to implement IoT in meaningful ways.
"What the IoT is all about is not tinkering and building the Raspberry Pi. It's about taking all the everyday things in our life and connecting them," Boyd said. "IoT is the new norm. This is just like Web and mobile. It is just the way now. It's certainly something that a lot of you should be thinking about as you look out at devices on your factory floor or agricultural scenarios."
Connecting those devices is where Azure comes in, and the services can be overwhelming. For example, when it comes to messaging, a developer might be confused by the options of Service Bus, Event Hubs or IoT Hub. All can be, and have been, used in IoT solutions. Boyd offered a succinct overview in his session.
"OK, there are all these messaging services in Azure. When do I use which service?" Boyd asked. "IoT Hub is built on Event Hubs. If you don't have a scenario where you have devices -- and I use that term loosely because that can mean a lot of things, but if you have applications where you're wanting to stream data in -- Event Hubs is the better solution for you. If you have devices, then IoT Hub is the right fit. We did IoT before IoT Hub in Azure using things like Service Bus. We built a massive kiosk network in Azure that you guys have all been customers of. But IoT Hub simplifies things [for IoT scenarios]."
Boyd also offered a way to think about the difference between IoT Central and IoT solution accelerators, two different services in the Azure catalog both intended for developers getting started with IoT. Both can get you up and running quickly, but IoT Central is more limiting. "It probably isn't your long-term strategy," Boyd explained.
"Azure IoT Central is a SaaS service. You can think of it like Office 365 for IoT. You can just go spin up a service really quickly without having to think about code. It's not a bad service. If you want to just kick the tires and prove something out and demo it to your executive group, it's great for that. It may be a good service to go pilot some things, as well," he said.
You can also get off to a quick start with the IoT solution accelerators, but those are much better as a starting point for an enterprise solution, he explained. The accelerators automatically spin up various IoT-related services for canonical, pre-built scenarios, including remote monitoring, connected factory, predictive maintenance or device simulation.
"This looks similar, but it's not the same," Boyd said of the accelerators in comparison to IoT Central. "You can modify it, redeploy it. The code for this dashboard, unlike IoT Central, is available to you, so you can tweak and customize it however you need it."
Posted by Scott Bekker on 12/06/2018 at 3:56 PM