There's been many presentations and articles on why it makes sense to use MongoDB for Single View of the Customer.Customers like Metlife widely adopted our technology and built applications never possible before (Read: Built in record time, the MetLife Wall knocks down barriers to great customer service). At MongoDB we believe this is a transformative use case and have spent a considerable amount time to explain the reasons why our technology should underpin such projects (Read: Single View use cases on MongoDB.com).
Lecture starts with an overview of traditional architectures, then goes through the key challenges for SCV, why Big Data makes things even worse and then highlights why MongoDB is such a natural fit. Slides below are self-explanatory, but let me quote a few key passages.
The business reasons to start your projects today:
- A customer data flaw in a demand forecasting system cost a major US airline $50 million in one year of operation…on top of the $40 million development cost to implement it
- When a global stationary retailer examined their views of a customer, it was found that every real customer had roughly 2.5 “virtual” customer records across 75 source data systems. Resulting cost was estimated as a net loss of 9% per customer transaction
Why should you use MongoDB as a platform:
- It solves many problems associated with existing RDBMS-based SVC solutions, especially in the areas of: Speed of Access, Speed of Comparison, Representation Flexibility, Data Flexibility and Reliability
- MongoDB provides a demonstrably lower Total Cost of Ownership than previous generation SVC solutions
Want to know more? Reach out to me or Rob directly or to your contacts at MongoDB.
See the full deck on slideshare:
