New video: Rule-based event management in IoT
One major goal of the Internet of Things (IoT) is the connection and interaction of systems and things. Formerly, most of those things were offline and not able to play a role in a networked world. Now, those kind of connected systems provide users added value by supplying services across domain boundaries, e.g. telemedicine, energy, mobility, smart homes. By integrating systems and things in this exciting, networked world, not only new stakeholders come into play, but also the number of situations grows immensely.
Systems report situations in the form of events, which carry not only domain specific data such as current temperature, energy consumption or health of a system. They also provide context information such as timestamp, location, ownership, historic data leading to a situation and sometimes even outage and failure of the system itself. Some events are correlated with others resulting in so called complex events. Others need to be filtered or routed to post-processing systems and users. There is one thing that all events have in common: Every reported event needs a decision on how to react. Due to the sheer mass of incoming events in a fully connected world, it is impossible for humans to make interactive decisions on a manual basis. Automated rule-based event management is the key.
My new video: What’s in for you?
- I will explain how the rule-based approach supports IoT system providers to automate decision-making, trigger interactive and automated processes and integrate third party systems to come up with an overall responsive, auditable and manageable system.
- I will show you how rules can be distributed across system boundaries. Why is this important? Firstly, you gain computing power of all systems connected to the Internet of Things (and not just the backend). Secondly, you are faster in distributed systems as you can react directly to events where and when they occur without the need to involve the backend. Nice benefit: You are more autonomous, in particular if you do not want to rely on network connectivity for backend access.