TRUVISO Continuous Analytics rss

Truviso Blog
Home Page Products Solutions Customers Resources Company Contact Us
Customer Support Login
Truviso Blog | Immediate Insight |

Truviso 3.2: Making Interoperability Simple and Safe

By Sailesh Krishnamurthy
November 25, 2009 @ 4:32 pm

Applications that load data typically operate in transactional fashion, where any failure because of software, hardware or network error results in the data loading transaction aborting, forcing the application client to re-load the appropriate data. The problem with this in most analytical event processing (AEP) and complex event processing (CEP) systems is that individual records that have already been processed by continuous queries have to be undone if those records are part of a data loading transaction that has been aborted. Delaying the processing of the data until the completion of the loading transaction leads to significant latency, and is therefore unacceptable in a real-time environment.

The Truviso Continuous Analytics version 3.2 release offers full dataset transactional consistency for data loading integrity. If all the records of a dataset are not successfully transmitted, the system is able to “unwind” its effects on all reports and analyses that were affected.

Truviso achieves transactional consistency by running two processes in parallel: (1) a “bookkeeping” protocol that tracks when a loading dataset begins and commits, and (2) a continuous processing activity that continually updates queries.  In the event of a transaction abort, the bookkeeping function records the partial state of the data load, and the system unwinds any committed data that will adversely affect results until the dataset re-loads. This function maintains the correct data state in a seamless and transparent fashion.

As a result, with Truviso v3.2, you can rely on your infrastructure to maintain data integrity, including when connecting the system with extract transform load (ETL) or other data-loading transactional applications. Another important application is when moving data around with a transactional message queue in order to guarantee that data is not lost anywhere. Best of all, the bookkeeping protocol is so lightweight that safety is accomplished without sacrificing any appreciable performance.

The ability to exploit deep RDBMS (relational database management system) integration enables Truviso to provide unmatched levels of data integrity – a major benefit that no AEP/CEP system can deliver because of their inherent architectural constraints.




© Truviso, Inc. 2009-2010. All Rights Reserved.
Truviso™, Continuous Analytics™, VIA™, TruCQ™, and TruView™ are trademarks of Truviso, Inc.