New Feature of Interference Cluster Release in Version 2021.1

Introduction

The 2021.1 version of the interference cluster has been released. (The previous article, in which I talk about the basic features of this software, can be found here.). Much attention was paid to improving overall performance and stability. In my opinion, an interesting feature has appeared, which I want to talk about in this short article.

Previously, the concept of the interference cluster was kept strictly within the framework of a server-side service that provided persistence and event interaction services to some server-side java applications. Since the concept of the interference as a database did not provide for JDBC connections, we could not access the data from the outside in any way. Any interactions were possible only between applications of the cluster nodes, each of which contains persistent storage.

A Guide to Rules Engines for IoT: CEP Engines

What Are CEP Engines?

Although part (and predecessors) of stream processing engines, Complex Event Processing engines deal with events in a slightly different (and better) way than their bigger and younger siblings.

We see CEP engines being deployed in edge computing nowadays, where locality, low latency, and low hardware footprint are important. CEPs are a good fit whenever a low footprint is required but don’t scale well since all event processing happens in-memory.