This Q&A is an excerpt from our June 27, 2016 webinar: Big Data: Mind the Gap, presented by Brad Anderson, Liaison Technologies VP Big Data Informatics
Question [Audience Member]: What could be an approach to go from application-centric to data-centric?
Answer [Brad Anderson]: If you think about an MDM or ERP system or CRM system, we find that when we go in and ask customers or prospects about these systems, they want three or four or five different features. But when you buy one, you get 100 features, and you get an implementation team—an army of consultants that are coming in to implement it—and there’s a lot of risk in these projects. This is the mindset nowadays of “I have to buy an application and I have to potentially even fit my business practice to that application because that’s how that application works.”
Well, think back to the slide where I talked about microservices and choosing the best data system for the data and for the use case. For example, the queries you’d like to ask, like the pattern-matching screens for a time series database, the patient matching, or the fraud detection, which is actually matching up bad behavior and your customers and their bank accounts and so on, that screams for a graph database, right? And so you’re using the proper tools, but the primary consideration there is your data. You’re thinking, “Okay, I have this data and I have this business outcome that I want to drive business value.” You’re not thinking of an application. You’re thinking about taking the three features of an MDM system—out of 100—and the two features that you want out of an ERP system or a CRM, and you’re going to string those microservices together in a configured manner that fits your business process. I think this is the mindset you have to get into to begin data-centric thinking and get out of the mindset of application-centric thinking.