How would you position NEsper next to existing solutions (or hacks) in the industry?
Nesper shares the same positioning as its name-sake. Nesper is the only CLR-based open source Event Stream Processing out there – and this is not to be confused with classical rules engines. Compared to commercial ESP engines implementations, Nesper may lack high availability options in the 1.3 release, but its open source nature is a driver to get the Event processing language right, and get the CLR community up to speed on those concepts – before tackling enterprise grade requirements in upcoming versions. Generally Rete-based production rule engines can indeed be used to address part of what CEP coins. Especially triggering by correlating events, possibly including a temporal relationship between events. That said the ESP side – Event Stream Processing – is a different beast, where what matters is the “S” for Stream. In this side of the Esper engine we provide several language facilities to build expressions using time not for temporal relationship (happened before etc) but for slid
