tag:blogger.com,1999:blog-7831813422886730737.post8015498947798321215..comments2023-10-08T10:44:28.524+03:00Comments on Event Processing Thinking: More on taxonomy and classification in event processingOpher Etzionhttp://www.blogger.com/profile/10791357917675270335noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-7831813422886730737.post-31061655230031303702010-01-21T01:51:57.450+02:002010-01-21T01:51:57.450+02:00Thanks for reviewing the post.
I meant to differe...Thanks for reviewing the post.<br /><br />I meant to differentiate between detection based on some understood interface or contract (e.g. detect that an order has been placed by getting an order event) and detection of events that are outside of defined or intended contracts (e.g. detect that an order may be a duplicate by checking against recent orders).<br /><br />The latter is what I meant by detection oriented EP. I would consider the former to be a part of the operation, along with the decisions and results.<br /><br />The simple cases of either detection and operation are generally equally simple and even similar.<br /><br />As functionality gets more complex, I have noticed that the detection (per my intended distinction) and operation grow farther apart in many practical concerns from value and requirements all the way to coding.<br /><br />Although it's possible that both detection and operation use the same EP patterns, I have observed separation in business understanding, development processes and non-functional requirements placed on the EP infrastructure.Hanshttps://www.blogger.com/profile/03057096345613832279noreply@blogger.com