In the first post in this series, we talked about the challenges of integrating the Internet of Things into the enterprise. In the next few blog posts, we are going to build a simple IoT application that illustrates all the major aspects of working with SnapLogic and hardware. In this post, we’re going to skip device details, but at a high level we’ll have:
- A sensor somewhere (on-premises, from an API, etc.) that produces data that includes a “color” payload;
- An LED on-premise, attached to our local network, conveniently hooked up to look like a REST endpoint;
- Two pipelines, one on-premise, one in the cloud.
Some IoT hardware is designed to be cloud-native, and will generally have a publish/subscribe relationship with a cloud server (such as MQTT). This is very easy to work with from a security standpoint, since the output of these devices are accessible from anywhere.
Other devices instead communicate on their local network. Assuming your local network isn’t internet accessible, this can create problems in talking to the device. Usefully, the SnapLogic Control Plane (depicted, in a manner of speaking, as the rightmost rectangle below) comes to our rescue here.