tag:blogger.com,1999:blog-3100335968062348807.post7431910249219552204..comments2024-01-13T19:18:24.437+01:00Comments on Facts and Thoughts: SOA, EDA and CEPAlexhttp://www.blogger.com/profile/02000951254466645137noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-3100335968062348807.post-54474987205596125152020-08-09T18:35:49.066+02:002020-08-09T18:35:49.066+02:00This comment has been removed by the author.Update Technologyhttps://www.blogger.com/profile/10999116357151662884noreply@blogger.comtag:blogger.com,1999:blog-3100335968062348807.post-17795068281128387422008-10-31T13:35:00.000+01:002008-10-31T13:35:00.000+01:00If I am being asked "tell me how CEP is revolution...If I am being asked "tell me how CEP is revolutionary", I'd argue this is because it provides an higher abstraction to deal with streams, time windows and causality as first class citizens in the programming/development/composition model (depending the implementation but end result is the same). An analogy would be procedural / object oriented programming. You can say it is evolution (and the name makes this explicit sometime to help adoption and promote reuse of past practice and knowledge - f.e. C++) but its revolutionary in its implications.Alexhttps://www.blogger.com/profile/02000951254466645137noreply@blogger.comtag:blogger.com,1999:blog-3100335968062348807.post-11961855179444815852008-10-31T01:51:00.000+01:002008-10-31T01:51:00.000+01:00Just because CEP evolved from other sensor and ind...Just because CEP evolved from other sensor and industrial processes, doesn't disqualify them from being "disruptive" (which obviously a subjective term). Most CEP-based solutions, in fact, don't even have an ESB - most use a middleware technology that's 24 years old - TIB. So I think that argues against "networking, ESBs, and standardization" as what's disruptive. <BR/><BR/>But even if we choose to disagree, whichever way you chose, events are indeed a good, modern, perhaps disruptive way of building modern applications.Mark Palmer, StreamBase CEOhttps://www.blogger.com/profile/00505562132817125644noreply@blogger.comtag:blogger.com,1999:blog-3100335968062348807.post-68276698588826548842008-10-30T14:40:00.000+01:002008-10-30T14:40:00.000+01:00@Mark,I think CEP is not really revolutionary eith...@Mark,<BR/><BR/>I think CEP is not really revolutionary either. Event processing and correlation evolved from interupt handling in computer systems and actuator/sensor technologies in industrial processes. Disruptive is that these technologies can now be applies to business events at an enterprise level. Thanks to networking, ESB, standaardization and generic event processors.<BR/><BR/>-JackJack van Hoofhttps://www.blogger.com/profile/10073941747649739657noreply@blogger.comtag:blogger.com,1999:blog-3100335968062348807.post-81944567841578736462008-10-30T04:03:00.000+01:002008-10-30T04:03:00.000+01:00Excellent post, very much agree, Alex, with the lo...Excellent post, very much agree, Alex, with the loose analogy that ESB is to SOA as CEP is to EDA. <BR/><BR/>However, I have one nit to pick on the subject of ESBs (not that your raised it, per se, but the analogy does). Having been involved with the creation of one ESB, IONA's Artix, and commercially with another, Sonic ESB, the notion that ESBs are disruptive is facile thinking. ESBs, although they are excellent tools, are simply an evolutionary technology, whose close ancesters were CORBA, DCE, and even simple sockets. ESBs were just a better, standards based version of these previous generations of middleware.<BR/><BR/>CEP, on the other hand, brings fundamentally disruptive capabilities to EDA; the ability to express event-based computing logic that's aware of streaming events, temporal relationships, causal relationships, and handle the volumes of event rates that are found in typical event driven systems - these are are revolutionary, not evolutionary, technology breakthroughs that ESB does not contain.<BR/><BR/>- Mark Palmer<BR/>http://streambase.typepad.com/streambase_stream_process/Mark Palmer, StreamBase CEOhttps://www.blogger.com/profile/00505562132817125644noreply@blogger.com