The UNIX and Linux Forums  

Go Back   The UNIX and Linux Forums > Special Forums > News, Links, Events and Announcements > Complex Event Processing RSS News
Google UNIX.COM


Complex Event Processing RSS News Aggregated RSS news on CEP, ESP and EP.

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Thoughts on the Bitter Pill iBot Complex Event Processing RSS News 0 02-13-2008 10:30 PM
2nd Generation SOA = EDA + CEP? iBot Complex Event Processing RSS News 0 11-28-2007 04:30 PM
Symark Software Named to Software Magazine’s Software 500 for ... - Business Wire (pr iBot UNIX and Linux RSS News 0 10-29-2007 05:40 AM
Shellcode Generation using C Legend986 High Level Programming 2 10-07-2007 10:25 PM

Reply
 
Submit Tools LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 02-08-2008
iBot's Avatar
RSS Robot Girl
 

Join Date: Sep 2000
Posts: 14,303
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit! Stumble this Post!Spurl this Post!
A Bitter Pill To Swallow: First Generation CEP Software Needs To Evolve

Tim Bass
Sat, 09 Feb 2008 03:08:55 +0000

Frankly speaking, the CEP market is now saturated with hype about all the great things CEP can do, detecting opportunities and threats in real time and supporting the decision cycle.* However, in my opinion, it is time, for the software vendors and analysts to move beyond the marketing hype and demonstrate real operational value with strong end user success, something seriously lacking today.
I have advocated this evolution for two years, including the notion of expanding CEP capabilities with proven techniques for event processing that have worked well long before current “Not yet CEP but called CEP” software hit the marketplace and airwaves.
For example, in my first CEP/EP presentation in New York in 1Q 2006, I presented Processing Patterns for Predictive*Business*and talked about how the US military has implemented high performance detection-oriented systems for many years (in the art-and-science of multisensor data fusion, MSDF),*and how every day, when we sit at home (or at work or in transit), we are comforted to know*we are safe from missile attacks because of what I*would also*call*”complex event processing.”***There is a very rich history of “CEP but not called CEP” behind the scenes keeping people*safe and warm. (The same thing can be said with many similar examples of complex event processing in use today, but not called “CEP” by CEP software vendors.)
This is one reasonw, when I read the “CEP history lessons,” I am amused at how, at times, the lessons appear self-serving, not end user serving.* There is so much rich event processing history and proven architectures in “CEP but not called CEP” (CEP that actually works, in practice everyday, long before it was called CEP).* It continues to puzzle me that a few people the CEP/EP community continue to take the “we invented EP” view.* Quite frankly, the history we read is missing most, if not all, of the history and practice of MSDF.
When we take the current CEP COTS software offerings*and apply it to these working “CEP but not called CEP” applications, the folks with real operational “CEP but not called CEP” detection-oriented experience quickly cut through the hype because they are, based on their state-of-the-practice, now seeking self-learning, self-healing “real CEP type” systems.* They are not so excited about first generation technologies*full of promises*from software vendors with only a few years of experience in solving detection-oriented problems and very few real success stories.
The same is true for advanced fraud detection and other state-of-the-art detection-oriented processing of “complex events” and situations.* The state-of-the-art of complex event processing, in practice, is far beyond the first generation CEP engines on the market today.*
This is one of the reasons I*have*agreed*with the IBM folks who are calling these first generation “CEP orchestration engines” BEP engines, because that view is closer to fact than fiction.* Frankly speaking again, process orchestration is much easier than complex detection with high detection confidence*with low false alarms.
Customers who are detection-savvy also know this, and I have blogged about a few of these meetings and customer concerns.* For example, please read my blog entry about a banker who was very sceptical in a recent wealth management conference in Bangkok.* I see this reaction all the time, in practice.*
Complex problems are not new and they still cry out for solutions.* Furthermore, many current-generation event processing solutions are already more advanced that the first generation CEP engines on the “call it CEP” market today.* This is a very real inhibitor, in my opinion,*to growth in the “call is CEP” software space today - and credibility may ultimately be “at risk.”* Caution is advised.
Candidly speaking again, there are too many red-herring CEP-related discussions and not enough solid results given the time software vendors have been promoting CEP/EP (again, this is simply my opinion).* The market is in danger of eventually losing credibility, at least in the circles I travel and complex*problems I enjoy solving, because the capabilities of the (so called) CEP technologies by software vendors in the (so called) CEP space have been over sold; and, frankly speaking, I have yet to see tangible proof of “real CEP capabilities” in the road maps and plans of the current CEP software vendors.* This is dissappointing.
This pill is bitter and difficult to swallow, but most of my life’s work has been advising, formulating*and architecting real-time solutions for the end user (the*C-level executives*and the*operational experts*with the complex problems to solve).** CEP software*must evolve and there needs to be more tangible results, not more marketing hype.



Source...
Reply With Quote
Google UNIX.COM
Forum Sponsor
Reply

Thread Tools
Display Modes


The 50 most popular UNIX and Linux searches.
Google Search Cloud for The UNIX and Linux Forums
"inappropriate ioctl for device" 421 service not available, remote server has closed connection ^m ascii eof autosys awk trim bash eval bash exec bash for loop bash subroutine boot: cannot open kernel/sparcv9/unix close_wait curses.h dead.letter find grep grep multiple lines grep or grep recursive grep unique inappropriate ioctl for device logrotate.conf lynx javascript mailx attachment make: fatal error: command failed for target `all-recursive' mget mtime perl array length ping port read awk output into multiple variables replace space by comma , perl script scp recursive segmentation fault(coredump) sftp batch sftp script snoop unix stale nfs file handle syn_sent tar exclude unix unix .profile unix com unix for loop unix forum unix forums unix interview questions unix memory usage unix mtime unix simulator unix.com while loop within while loop shell script


All times are GMT -7. The time now is 05:19 PM.


Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited.
The UNIX and Linux Forums Content Copyright ©1993-2008 The CEP Blog All Rights Reserved -Ad Management by RedTyger Visit The Global Fact Book

Content Relevant URLs by vBSEO 3.2.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102