Complex Event Processing RSS News

lundberg
08-19-2008 04:01 PM
My colleague, Paul, got lots of… let’s call it, “feedback” regarding his post on the impending demise of the standalone Business Rule Engine (BRE) Market. It seems there are lots of folks out there who feel quite passionate about the subject, so I thought I would continue, albeit from a different angle and relate it back to the CEP and BusinessEvents for comparison.

So… taking my cue from David Letterman and with a tip o’ the hat to Paul, here are the:

Top 10 reasons why TIBCO BusinessEvents (BE) beats a simple Business Rule Engine + JMS layer (remember, no wagering please)

10. BE is Standards-based (for concept/class models, state models, rule models etc)

9. BE requires no app server or RDBMS (for lower cost, and quicker deployment)

8. BE provides multiple options to extend to other event channel types (for flexible complex event processing)

7. BE has Rule / decision management (for business control of software services)

6. BE takes a co-operative agent approach (for co-operating components and event processing services)

5. BE supports high scalability (for parallelizing applications and eXtreme Transaction Processing)

4. BE supports queries as well as rules (for dynamic facts)

3. BE supports State Models as well as rules (for case management, entity lifecycles, etc)

2. BE is designed as a stateful approach (for saving temporal information between messages)

and the number 1 reason is…

1. Real-time event-driven support already built in to the BE rule engine (for efficient Event-Driven Architecture use)



Source...