CEP The Concept Is Not CEP The Software
Paul Vincent misquotes me in his recent post, Situation Awareness in CEP…. So, keep your eyes on the blog-o-rink because it looks like there may be a lot of sparks flying between bloggers over the next few days or weeks on this topic. The problem with many folks in this dialog is that they do not not clearly distinguish between “CEP the concept,” and “CEP the software”.
Many will recall that I illustrated the connection and application of CEP to Situational Awareness (SA) when I introduced the JDL to CEP. The JDL is the most mature abstraction we have for expressing how SA is achieved from a functional perspective. In addition, I have a March 2006 keynote (as a TIBCO employee) were I mentioned that SA/CEP requires much more sophisticated methods and algorithms than what software sellers were selling as CEP. Little, if anything, has changed since then - except the hype-o-meter has moved more to the right.
As I mentioned to Paul in his blog, TIBCO engineers have never disputed this assertion. TIBCO’s BE has not yet evolved to the point of being truely “SA capable”, in my opinion; and BE is heads and shoulders above the competition.
CEP “The Concept” does not equal “The Software Marketed as CEP”.
One of the trouble with many (software) companies is that they are so preoccupied with positioning TLAs like CEP, EDA, SOA, BRMS and so forth and so on; while at the same time positioning their software as CEP, EDA, SOA, BRMS and so forth and so on; that they blur the distinction between software and it’s current capabilities and the long term engineering goals - the end game.
Filed under: CEP News and Events, CEP Terminology, CEP Tutorials, Complex Event Processing, Event Processing
