tag:blogger.com,1999:blog-7831813422886730737.post860170474952397054..comments2023-10-08T10:44:28.524+03:00Comments on Event Processing Thinking: Unplanned events - againOpher Etzionhttp://www.blogger.com/profile/10791357917675270335noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7831813422886730737.post-4833175063839178322008-01-22T16:52:00.000+02:002008-01-22T16:52:00.000+02:00Congratulations on your fast reactions, and commis...Congratulations on your fast reactions, and commiserations on the slower reactions of the driver behind. Clearly there are some events you have to process in real time. But I hope you are not implying that all events must be processed in real-time. When the fuel tank indicator appears, do you refuel immediately or do you wait until you reach the next gas station? How often do you have the vehicle serviced?<BR/><BR/>I think the critical question for systems designers here is to determine which are the events that call for a real-time response, and which are the events where a batch response is more appropriate.<BR/><BR/>Surely the event infrastructure should be capable of handling both.Richard Veryardhttps://www.blogger.com/profile/04499123397533975655noreply@blogger.comtag:blogger.com,1999:blog-7831813422886730737.post-74366100132230129912008-01-22T09:45:00.000+02:002008-01-22T09:45:00.000+02:00That's a good proof for real-time event processing...That's a good proof for real-time event processing, and for the advantage of big, heavy, cars. It is also a demonstration of the need to share events. If the driver behind you had the knowledge that you had when breaking, her (or his) behavior would be different.Eranhttps://www.blogger.com/profile/15249363784380760219noreply@blogger.com