Matching MDM with Hadoop: Think of the Possibilities by Loraine Lawson.
From the post:
I’m always curious about use cases with Hadoop, mostly because I feel there’s a lot of unexplored potential still.
For example, could Hadoop make it easier to achieve master data management’s goal of a “single version of the customer” from large datasets? During a recent interview with IT Business Edge, Ciaran Dynes said the idea has a lot of potential, especially when you consider that customer records from, say, banks can have up to 150 different attributes.
Hadoop can allow you to explore as many dimensions and attributes you want, he explained.
“They have every flavor of your address and duplications of your address, for that matter, in that same record,” Dynes, Talend’s senior director of product management and product marketing, said. “What Hadoop allows you to consider is, ‘Let’s put it all up there for the problems that they’re presenting like a single version of the customer.’”
Dynes also thinks we’re still exploring the edges of Hadoop’s potential to change information management.
“We genuinely think it is going to probably have a bigger effect on the industry than the cloud,” he said. “Its opening up possibilities that we didn’t think we could look at in terms of analytics, would be one thing. But I think there’s so many applications for this technology and so many ways of thinking about how you integrate your entire company that I do think it’ll have a profound effect on the industry.”
When I hear the phrase “…single version of the customer…” I think of David Loshin’s “A Good Example of Semantic Inconsistency” (my pointer with comments)
David illustrates that “customer” is a term fraught were complexity.
Having a bigger gun doesn’t make a moving target easier to hit.
Can do more damage unintentionally than good.