What would be the outcome if you commissioned a group of traditional reference data management experts to build the World Wide Web back in the early ‘90s? As a renowned expert in data modeling, your only solution is to build a data model, identifying all attributes and relationships to be used for the sum of experiences demanded by the user.
You have gifts as a Data Modeler your peers can only dream of. And who cares if you end up with 25,000 attributes in your data model – you understand them far better than any mere mortal could and are determined to show your mastery of modelling tools. CERN will be impressed. You would tell CERN as long as they put in place the right “governance” process all will be well.
Thankfully this wasn’t the approach taken in CERN when building the original World Wide Web. The complexity of non-stop change, massive data volume, conflicting demands and classifications of data is what the World Wide Web is known for. The future of reference data management needs to take the same approach.
We have gotten to a stage where traditional reference data management approaches have outlived their useful life. The demands of reference data management in 2010 are far beyond what was envisaged 15-20 years ago, where the roots of today’s data model-centric solutions lie. The world then was one of known knowns, a couple of feeds, simple asset classes and a handful of data consumers.
Innovations in Trading and Technology (
Comments | Post a Comment
2 Comments to "Has Reference Data Outgrown the Humble Data Model?":
shalom
20 December 2010
To me, ref data encompasses (a) symbology mappings (b) product terms (including issuing entity) and (c) EOD pricing. The complaint about "25,000" attributes" sounds familiar - just look at what SWIFT does in this area. However, you might like to look at how FIXML models security attributes. You get small "feature" building blocks to describe a security and can combine them in infinate ways - which is close to what financial engineers are doing. For intraday pricing, just get a good tick DB.
Comments (17)
hanweck
22 December 2010
To me, the real problems with reference data are: quality (even the exchanges publish errors), cost (it's a revenue generator for the exchanges or broker/dealers) and licensing (just look at CUSIP). RDBMSs happily process hundreds of billions of records, and fast intrday updates, without any troubles... certainly fast enough to accommodate even intraday pricings. Hanweck Associates' VoleraFEED and VoleraRISK products process real-time listed options data -- over a million contracts globally -- computing real-time options analytics and portfolio risk. For these applications, off-the-shelf RDBMSs are more than adequate to handle reference data.
Comments (5)