To me it looks like a "paid for analyst coverage" (aka advertorial), as I can't believe the author would not do some basic research and find:
- "It has the ability to process both CEP style events and log events (it is simply a question of building the right adapter, if it does not already exist)" - true for all CEP tools AFAIK
- "as well as what the company describes as continuous ETL (extract, transform and load)" - already a use case for existing CEP tools like TIBCO -
http://tibcoblogs.com/cep/2007/11/24/cep-as-sauce-for-alphabet-soup-part-9-etl/- "differences ... it operates in the database layer and not in the application server tier" - I guess the author hasn't heard of Oracle or Sybase (and their new Coral8-based features)? And I'm sure "app serving" is NOT the same as "event processing", and that v few CEP tools if any work against a conventional app server! In any case most CEP tools can access the DB layer if they need to...
- "operates in the database layer ... I regard this as a good thing because it should improve performance." OK, I spilt my coffee over that one! No disrespect to the DB guys, but if you could do all event processing in a standard database the CEP tool industry wouldn't have got out of bed!
- "has used SQL wherever it can so that extensions are minimal" - this has always been a selling point for all SQL-based stream processing tools?
So it looks like an advertorial or uninformed analysis - and hence David's dilemna. As I am not as polite as David I would feature it and rebuke it in the same entry! But kudos to the vendor involved for the gorilla marketing and increasing the awareness of CEP...