With the advent of IoT (Internet-of-Things), sensor-based applications are no longer confined to the factory floor, sensor-enabled systems are now all around us: in cars, appliances, smartphones, buildings, cities etc. From a back-end perspective, IoT systems are no longer based on closed, fit-for-purpose architectures as their M2M predecessors, but are able to interact with other applications and open to future innovations.

The power lies in the integrations

Most of us will acknowledge that great applications can be created by combining sensor data streams with other information available in either company internal IT systems or API information available on the Internet.

A couple of examples to clarify what I mean:

What these examples all have in common is that they combine information available in API-format on the internet with information coming from real devices in order to enrich the application and to contextualize it.

Achieving this is not without particular technical challenges, one of which I would like to focus on today.

The programmable internet vs the programmable world

On the internet and broader IT world, most data retrieval models are query-based: whenever you need a piece of information, you query an API to retrieve that piece of information.

Here are some examples:

The Internet of Things on the other hand, is the world where sensor data is produced, and contrary to the model above, rather than waiting for you to fetch the data, this sensor data gets pushed to you. MQTT, the popular IoT messaging protocol, is based on a publish-subscribe mechanism where you subscribe to events or data streams from a particular source. Critical in IoT is the ability to process data in real-time as it comes in, i.e. the ability to act on data in motion. With periodic polling, some scenarios will just break down: if I arrive at the office (an event based on my location), I want the lights switched on right away, not with a 15 minute delay… I guess you get what I mean.

Much of the existing technology is either optimized to work query-based or to determine patterns or correlate event streams. In other words, it’s optimized for solving a subset of the problem space. So here’s our vision: in order to bring IT and IoT closer together, we need technology that can effortlessly blend event-based and query based data in real-time (instead of one or the other), hiding underlying technical complexity from users and extending the idea of a programmable internet to a real-time programmable world.

We have built Waylay based on this vision, sign-up for a demo to learn more on how our engine works.

You might also like these articles

Waylay Digital Twin

How to improve customer support & field service for connected IoT assets with Waylay Digital Twin for Salesforce

Waylay Digital Twin

7 ways to improve field service with IoT asset visibility

IoT Insights

Challenges of creating Digital Twins in the transition to Industry 4.0