Transactional JVM in CEP?
Posted by Paul Vincent
Another interesting TIBCO technology acquisition with potential side effects for high performance event-processing: the Kabira transactional JVM has joined the TIBCO team. This provides a JVM (called Fluency) that has built-in (to quote the developer guide):
• Transactions
• Distribution
• Shared Memory Persistence
• Keys and Queries
• High Availability
• Replication
Transactional integrity is of course orthogonal to event processing: some event processes, especially those that impact multiple services and processes, need a transactional context. In complex event processing, identifying complex events is rarely “transactional” per se, but could depend on some state / include some transactional context. And of course, the business process associated with a complex event may well need to be a transaction…
Tags: Fluency, Kabira, transactions
Complex Event Processing (CEP), Semantics | 26 April 2010 |
2 Comments
Other Links to this Post
RSS feed for comments on this post. TrackBack URI
By Paul Vincent, May 8, 2010 @ 09:17
Now that is interesting: lots of people finding this announcement interesting enough to vote on, but no-one commenting?
Hmmmm…
I’ll follow up with more on Fluency and high performance transactions / event processing / rules in a later post!
Cheers
By chris clabaugh, May 13, 2010 @ 11:30
Tibco can now truly represent that it provides one transactional view of a business, from high-latency ESB connected business applications, all the way down to low-latency elements through a network service bus.