tRDC – Reference Data Cache

Reference data is essential for various internal systems in financial institutions. Each request and sometimes even each requesting user generate costs that should not be underestimated.

The Be Reference Data Cache (tRDC) was designed to reduce costs for requests of Bloomberg master and reference data by caching and re-using data already received.
In case that a reference data request can be answered entirely by data already cached in tRDC, Bloomberg will not be involved at all. For tracking the achieved savings the tRDC provides a statistic including how many data requests have been answered by the cache and how many had to be sent to data provider Bloomberg.

Your benefits:

The tRDC is able to associate a so called “query policy” to each requesting system. Based on this query policy the tRDC decides which timeliness of data is acceptable. If necessary, the option to configure a direct routing to Bloomberg to bypass the cache, exists.
The access to the tRDC is entitled on the consumer system level.
The tRDC operates on a fully persistent database, which ensures quick recovery while still having full data coverage. Any relational database management system supporting JDBC may be used for data storage.
The tRDC comes with a component to handle the SFTP communication with the Bloomberg servers, but it is even able to operate on the local file system for customers who provide their own SFTP communication layer.