The Data Roundtable
A community of data management experts
Master Data Access Use Case #2: The Composite Record
In the last post we looked at the use case for master data in which the consuming application expected a single unique representative record for each unique entity. This would be valuable in situations for batch accesses like SQL queries where aggregates are associated with one and only one entity record.
The snap, crackle and pop of data management on Hadoop
Data. It's everywhere. It can reside in many places through replication, accessibility needs or infrastructure costs. For reporting, that same data can be structurally changed (denormalized or aggregated) into additional reporting and analytic data repositories. Over time, new sources of enrichment of that data become available through traditional data sources
When data isn't sticky enough to keep customers
.@philsimon on the stickiness of data