tag:blogger.com,1999:blog-7831813422886730737.post1980592737068674558..comments2023-10-08T10:44:28.524+03:00Comments on Event Processing Thinking: Is event processing a subset of X ?Opher Etzionhttp://www.blogger.com/profile/10791357917675270335noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-7831813422886730737.post-46093542042212646042009-10-03T22:17:40.172+02:002009-10-03T22:17:40.172+02:00Opher,
This is a good blog as always. I've b...Opher, <br /><br />This is a good blog as always. I've been super busy at work, and haven't been responding as much as I'd like.<br /><br />Regarding your comment about event processing being a generic technology:<br />-- It's true that one way to look at event processing is generic, and we could engage in discussions about how to classify technology<br />-- But, that's a vendor view-point. What are the products, how do they integrate? <br />-- And assumes some degree of account control with the customer to sell product segments<br />-- But what about event processing in the large, and what can we do to use it in society, industry, govt?<br /><br />You know, we've discussed "very large event processing" (VLEPN) before, and there is no single product that could fill the (operational) need, but there may be concepts, tools and products to help fill an architectural need. A community VLEPN architecture.<br /><br />For example, let's say that a group of federal, state, local, tribal, orgs want to improve response to emergencies. Right now there are struggles over who has control, the "top dog" then tries to build a system where everyone has to pour their data into, then the "top dog" can have situational awareness, be able to make decisions, etc.<br /><br />The paradox, is that these types of communities are network based, and event based, and the situation begs a community-owned VLEPN architecture. Different orgs can field DBs, CEPs, BPMs, etc. but they would all have different owners, and be introduced at different times.<br /><br />A community owned VLEPN architecture would certainly have language aspects, technology aspects, acquisition, operations, etc.<br /><br />Thoughts?<br />++harveyAnonymoushttps://www.blogger.com/profile/16159576367477007568noreply@blogger.com