Biceps / News: Recent posts

I gave it some more thought and decided that it's best to avoid having a project name close to another existing project, even if it's not quite the same. Especially if I can easily do one better. So, the new project name is Triceps (triceps.sf.net), and the development has moved there. This old project location will stay for a little while as a pointer, and then will be deleted.

I've been feeling proud of how I've pickes such an obviously cute name for the project. Well, too cute. Turns out, that there is another project called BiCEP, in Portugal, at University of Coimbra. But they don't develop a CEP engine, instead they develop performance criteria that can be used to measure a CEP engine. With that and the spelling difference, it looks different enough.

CEP is an acronym that seems to be settled down now for the field of Complex Event Processing. The idea is to receive the streams of input events, process them in a database-like fashion and produce the streams of result events.

There is more than one approach to it. My favorite one is to think of it like a database driven by triggers. The incoming events produce the initial triggers, the processing percolates through the schema, and finally some triggers send the result events. It can be also thought of as a data flow machine (though if the topology contains loops, thinbgs become a bit interesting). Or as an industrial-strength spreadsheet.... read more

The work on the fundamental CEP features is going on. Sorry, no snapshots yet, but it can be extracted from svn. The features appear in the C++ API first, and then the Perl API gets added. No docs yet either, othern than the comments and examples.