Triceps is an innovative embeddable Complex Event Processing (CEP) system. It can be thought of as an in-memory database driven by triggers, or a data-flow machine working on a stream of events, or a spreadsheet on steroids. The major architectural advantages of Triceps include the direct use of procedural logic (as opposed to all-SQL systems), support of both compiled and general scripting languages (C++, Perl), light weight, and easy extensibility.
|Tags||cep esp event stream processing complex event processing database engines in-memory Database Database Engines/Servers Libraries Perl Modules|
Release Notes: This is another snapshot on the way to release 2.0, with the focus on build system improvements. Detection of the NSPR library has been made automatic, and hopefully now will build out of the box pretty much everywhere. Even if NSPR is not available, this release just uses the implementation of the atomic integers through the mutexes. A dependency of the messages in the Perl tests on the English locale has been found, and is solved by using the C locale for the tests.
Release Notes: This snapshot is essentially a pre-release for version 2.0 of the Triceps Complex Event Processing system. In addition to the updates from the last snapshot, it includes the multithreading framework. As usual with the snapshots, the Developer's Guide has not been updated yet, and the recent documentation can be found on the project blog. Some of that documentation is still being written.
Release Notes: This snapshot release includes the streaming functions, the Trivial Query Language, and the improved scheduling logic. As is usual with the snapshots, the Developer's Guide in the package has not been updated. Instead, the project blog serves as the interim documentation. The posts with the label 1_1_0 up to now describe all the new features.
Release Notes: This release fixes the versioning information in the Perl modules for submission to CPAN.
Release Notes: This is the first full official release that has all of the basic functionality. It includes the complete manual for the Perl API. The Developer's Guide is the size of a decent book, and is a good reading even if you are using a commercial CEP system and want to understand what is going on under the hood.