How does NEsper hook into an existing event-based system?
Today, event based system are often confused with message based system and/or Enterprise Service Bus architectures(ESB). Messaging system are event based but usually do not correlate events or process event streams at all. They simply process unitary events – and it becomes quickly complex if you need to correlate messages. NEsper can hook into any CLR based system as a message consumer – whose main purpose would be to listen efficiently to everything whilst sending back other events when a matching condition has occured. On the other hand, hooking NEsper in a classic messaging system allows having it correlate events even if those come from non-CLR based systems. This is just an example. NEsper is completely container agnostic, can run as a standalone component, and the 1.0 release simply assumes events to be plain objects. We are currently working on providing native XML format support as well.
