![]() |
|
| Customer Case Study – Customer Classification | ||||||||
Large Financial Services Institution – Classifying Customer TransactionsSQLstream's RAMMS provided an elegant and cost effective management platform for their existing applications built to classify customer transactions in real-time. There are many reasons why such companies wish to classify customers’ transactions in real-time: fraudulent or suspicious behavior, customers placed on a “watch list,” cross-selling, error detection, continuous reconciliation checking, performance monitoring, and so on. The list of possibilities is long. In this case, the nature of the classification is covered by a strict non-disclosure agreement, so we are not at liberty to share further information. The customer had already built for themselves a solution to process and to classify the transaction streams of a large number of its end user customers, using home grown algorithms represented in Java. Our customer had followed the progress of SQLstream and had seen us transform the RAMMS concepts into products with over a million lines of carefully crafted code over a period of several years. The customer had bought into the concept of RAM and RAMMS as a natural paradigm for combating the complexity of managing and processing dynamic data assets. The customer particularly valued a number of key elements of the SQLstream solution set:
We demonstrated how our SQLstream RAMMS platform would allow the customer to migrate their existing investment in Java stream processing. It would allow them to model their Java modules as a set of reusable components as plug-ins within our architecture, while embracing the SQL:2003 UDX standards for User Defined Transforms. Our central value proposition was our management and declarative processing capabilities. Some immediate benefits:
SQLstream's RAMMS provided a future-proofed architecture with a lower cost of ownership and low impedance into the rest of the organization, due to our strong support for standards for both SQL and metadata processing. Database LimitationsDatabases are excellent repositories of historical information, but have a lot of limitations in terms of being able to react in real-time or near real-time to changes in such data. There might be potentially thousands of queries to be run or other processing tasks that are required to be performed upon new or changed service data. Here are some of the activities that might need to be performed:
SQLstream's RAMMS provides a much more scalable and responsive SQL-based engine for managing, reusing, transforming and auctioning data than RDBMS. |
||||||||