tRDC - targit Reference Data Cache

tRDC – targit Reference Data Cache

Requesting reference data

Reference data like master data, end-of-day prices, and other low-frequency data is received by
various internal systems from different market data providers in financial institutions. Each request and sometimes even each requesting user can cause costs, which must not be underestimated.

Functionality of tRDC

The tRDC was designed to reduce costs for requests of reference data by caching and re-using data already received. It is able to offer reference data of different data providers to internal systems via a single technical interface and data format.

All requests are sent directly to the tRDC, which selects the best-fitting data source on the basis of configurable criteria as timeliness of information, priority of data sources or costs. The response data of these requests is cached in a standardized format and can be re-used as a basis for following

In case a reference data request can be answered thoroughly by data already cached in tRDC, no data provider has to be involved at all. Thus no further costs arise. Requests, which can only be served partly by the tRDC, will be sent to a data provider only for the data missing. Consequently, there is only a part of the costs to pay. The data provider’s response is then inserted into the cache and completed in order to answer the entire request.

To track the achieved savings, tRDC provides a statistic listing on how many data requests have been answered by the cache and how many had to be sent to a data provider.



For further information please contact or visit our website on


Product and service specifications
• DB2
• Oracle
• Sybase
Language used
• Java
Operating system
• Linux
• Solaris
• Windows 2003
Pricing structure
• Other
User interface
• Other
Market Data, Reference Data, Cache, Cost Reduction