Ruma Sanyal's Blog
Ruma Sanyal's Homepage
Ruma Sanyal is the Director of Product Marketing for
BEA's Event Driven SOA strategy and products. Ruma has an extensive
background in EDA, SOA, BPM, Integration, and Composite Applications.
Ruma has worked in engineering, product management, consulting roles at
Oracle, Bain, and HP and holds a Masters degree in Computer Science and
has an MBA from the Wharton School of Business.
CEP Engine or Event Driven Application Server?
Posted by rsanyal on July 10, 2007 at 4:32 PM | Permalink
| Comments (0)
Till date customers have been predominantly using CEP engines for event driven applications. In this setup their custom business logic typically runs on home-grown infrastructure or infrequently on application servers. However, these infrastructures cannot provide the support required to uniquely develop, deploy, and run (in a production setting) event-driven applications. A home-grown infrastructure support has limitations of scaling and performance (among other things). A general purpose application server does not support constructs and services required for event-driven programming. As the volume and speed of unpredictable events impacting a customers' top-line or bottom-line grows, customers would need robust infrastructure purpose-built for event processing. So, what would an event processing infrastructure look like?
An event-driven application server is a one-stop shop for customers' current and future event-processing needs. It would provide customers with ability to characterize & support event processing concepts like event sources, event sinks, event processors, and event streams, including the support for many to many relationships between all these constructs. It would contain well publicized, public interfaces for characterizing and extending all of the above artifacts. It would support a well-known (standards-based?) event processing language to specify event processing rules (and not use proprietary rules language). It would be able to support third party CEP engines (which is only a part of the overall event processing infrastructure) as one or more of the processing engines. Event processing services like thread scheduling, IO connection management, timer services, monitoring services, etc would also be available to customers to leverage and customize. Support for standards-based languages for configuration and meta-data definition will be provided. Building this infrastructure as a set of SOA services would also be beneficial from a componentization and customization perspective.
Infrastructure vendors have the inherent advantage of owning the complete stack. Hence leveraging their experience to build an application server for the specific purpose of event processing would be much easier, in contrast to a traditional CEP engine vendor which may run alongside a third party application server. As customers' needs for event-processing grow, a modular SOA-based event-driven application server is the way to accommodate these requirements flexibly, at a rapid speed, and cost effectively.
 |
|
October 2007
| Sun |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
| |
1 |
2 |
3 |
4 |
5 |
6 |
| 7 |
8 |
9 |
10 |
11 |
12 |
13 |
| 14 |
15 |
16 |
17 |
18 |
19 |
20 |
| 21 |
22 |
23 |
24 |
25 |
26 |
27 |
| 28 |
29 |
30 |
31 |
|
|
|
Search this blog:
Archives
July 2007
Categories
Product: WebLogic Event Server
Product: WebLogic Real Time
Recent Entries
CEP Engine or Event Driven Application Server?
|
