WSO2 Complex Event Processor 4.1 released 23rd February 2016.
This release mainly focuses on improving and stabilizing the product and enhancing its capabilities.
One of the main features that was included in this release is instrumenting and monitoring support for WSO2CEP as well as Siddhi. This enable users to identify throughput and memory consumption of each and every component of WSO2CEP and Siddhi. Through this users can identify possible bottlenecks in their queries and optimize CEP for better performance.
The same is also exposed via JMX such that It can be monitored to third party JMX consumers such as jconsole.
Another important feature CEP introduced in this release is visualizing Siddhi queries.
One of the notable improvement of this release is its improved high-availability support. now CEP can support high availability with more than two nodes providing zero downtime with no data loss, and as it also stores its state as a periodic snapshot to a database even during full cluster restart CEP has the capability of restoring it state from its last available snapshot. For more information refer the documentation here.
Further WSO2CEP has introduced several improvements to it’s core runtime complex event processor engine Siddhi. They are as follows:
- Hazelcast Event Table - Allowing events to be stored and manipulated in Hazelcast based In-Memory Data Grid.
- Minima and Maxima detection - Detecting maxima and minima in an event pattern, this allows detecting complex stock market patterns using combinations of maxima and minima.
- Map extension - This is introduced to support arbitrary key value pairs in Siddhi which was not supported for a long time. This function allows users to create a map, add remove and check for keys and values within a hash map.
- InsertOrUpdate to Event Table - This facilitate doing and insert or an update as an atomic operation on Even Tables.
- Outer and left joins in Siddhi - In addition to inner joins Siddhi now supports outer and left joins
- Time length window - The eviction policy on Siddhi window is triggered both by time and length properties.
- External Batch window - Allowing batch window to get triggered by event time rather by getting triggered by the system time.