Esper Content on InfoQ
Latest featured content about Esper

- Topics
- Workflow / BPM,
- Java
OSWorkflow by Diego Adrian Naya Lazo discusses the open-source OSWorkflow, a Java-based workflow engine. The book's publisher, Packt Publishing, also provided InfoQ with an excerpt from Chapter 4 of the book, entitled Using OSWorkflow in your Application. InfoQ spoke with Naya Lazo about the areas that the book covers and about OSWorkflow in general.
News about Esper
- Topics
- Java,
- Messaging
Esper is an event stream processing (ESP) and event correlation engine (CEP) that triggers actions when event conditions occurs among event streams - which can be thought of as a database turned upside down where statements are registered and data streams flow through. InfoQ caught up with Esper founders on recent project status, including BEA's use of Esper, and recent benchmarks.
- Topics
- Java,
- Application Servers,
- Real Time,
- Architecture,
- Messaging
A look at how BEA's WebLogic Event Server simplifies building Complex Event Processing applications.
- Topics
- Real Time,
- Java,
- Messaging
BEA recently announced WebLogic Event Server, a Java application server designed for event-driven applications and WebLogic Real Time 2.0 a new release of BEA's real-time technology.
- Topics
- Java,
- Messaging
At Java One Thomas Bernhardt and Alexandre Vasseur explained the concepts of event driven application servers and the Esper project.
Event driven application servers are a new category of servers, proving a runtime and supporting infrastructure services (transport, security, event journaling, high availability, connectors, etc.) to servers designed to be able to process over 100,000 events/sec.
- Topics
- Workflow / BPM,
- Java,
- Messaging
Esper is an event stream processing (ESP) and event correlation engine (CEP) unveiled this week with a 1.0 launch on Codehaus. Esper is a real time engine that triggers actions when pojo event conditions occurs among event streams. It is designed for high volume event correlation where millions of events coming in would make it impossible to use a classical RDBMS approach.