Other Industries

CR-X lends itself to a wide range of uses as a component of a solution, or as a solution in its own right. CR-X can be seen as an OEM plug-in, or as a pre/post-processor for major enterprise applications such as billing, event mediation/aggregation, traffic management and data warehousing.

Comparative Processing Models

In the processing model for a typical CR-X solution, input data is interpreted and directly processed to an output form according to business rules. This process model lends itself equally well to both batch and real-time data flows.

In contrast to the CR-X processing model, a generic RDBMS-based solution for the transaction processing domain, pictured below, has a number of sequential steps. Using RDBMS, input data must be first loaded into tables and indexed according to some internal data model. Business rules are applied to this data, resulting in the population of output data tables. These output tables must then be unloaded into an output data format. Such a model adds inherent complexity, latency, resource consumption, recovery issues and potential sources of error.

The diagram below illustrates how the strengths of CR-X complement the strengths of a relational database in the overall solution space

RDBMS solutions have a natural fit where there are moderate to high data relationship complexities (i.e. large data models) and where there are low to moderate transaction rates.

CR-X, on the other hand is very comfortable managing the entire spectrum of solutions - from low to very high transaction throughputs, with low to moderate data relationship complexities.