Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Business Track: How MongoDB Helps Telefonia Digital Accelerate Time to Market


Published on

Published in: Technology
  • Be the first to comment

Business Track: How MongoDB Helps Telefonia Digital Accelerate Time to Market

  1. 1. MongoDB NYC 2013A MongoDB use case atTelefonica DigitalPablo Enfedaque@pablitoev56
  2. 2. 2Telefonica DigitalExecutive summary•  We built the Personalisation Server using Oracle 11g•  We had performance issues with Oracle•  We built a new version with MongoDB in 4 months half the team•  We obtained great benefits§  Performance boost (one order of magnitude), predictable scaling§  Low time to market and better extensibility§  New opportunities for other products and services01
  3. 3. Título del capítuloMáximo 3 líneas01Telefonica Digital.Who we are?
  4. 4. 4Telefonica DigitalWho we are•  Telefonica§  Fourth largest telecommunications company in the world§  Operations in Europe (7 countries), USA and Latam (15 countries)§  315M of customers with Movistar, O2, Vivo, Terra…•  Telefonica Digital§  “Beyond connectivity”, division for web and mobile services & contents§  Jajah, Tokbox, Terra, TU, OWD / Firefox OS…01
  5. 5. 5Telefonica DigitalWho we are•  Telefonica Product Development and Innovation unit•  Around 70 different on going projects§  1 year, 6 months, 3 months or even 10 days projects01
  6. 6. Título del capítuloMáximo 3 líneas02Personalisation Server.Why?
  7. 7. 7Telefonica PDIPersonalisation Server. Why?•  We were storing profile data of millions of customers. However…01
  8. 8. 8Telefonica PDIPersonalisation Server. Why?•  We were storing profile data of millions of customers. However…§  Each service had its own internal storage§  Customers profile was scattered across a variety of different DBs§  In some cases stored in a DWH, others in isolated DBs§  No homogeneous interfaces or data structure§  Repeated or out-dated information01
  9. 9. 9Telefonica PDIPersonalisation Server. Why?•  We were storing profile data of millions of customers. However…Customers data was neither shared nor usable01
  10. 10. 10Telefonica PDIPersonalisation Server. Why?01
  11. 11. 11Telefonica PDIPersonalisation Server. Why?•  Personalisation Server as master customer’s data storage§  Operational storage, real-time access§  Flexible customer’s profile structure, classified in services§  Data sharing across all services§  Massive off-line batch interface§  Authentication and fine grained authorization§  Fault tolerance and high availability§  Inexpensive solution, low hardware requirements01
  12. 12. Título del capítuloMáximo 3 líneas03Oracle-based solution
  13. 13. 13Telefonica PDIOracle-based solution•  20 people involved (7 developers) in 14 – 15 months•  Oracle 11g Standard or Enterprise•  Three instances deployed•  Three iterations, focusing on performance enhancements01
  14. 14. 14Telefonica PDIAfter three iterations•  Three successful deployments, but…§  Oversized storage requirements§  Performance below expectationsStill not scaling enough04
  15. 15. 15Telefonica PDIThe fourth deployment arrived•  Everything went fine until one month before deploying•  New performance requirements appeared§  40% more data to be stored and processed§  Reload the whole DWH (22M customers) daily in small time window•  Servers already purchased01
  16. 16. 16Telefonica PDIHuge improvement needed•  Reduce storage to a half•  Enhance performance up to 3 times•  Only 4 months with a reduced teamFourth iteration with Oracle or move to a new technology?01
  17. 17. Título del capítuloMáximo 3 líneas04MongoDB-based solution
  18. 18. 18Telefonica PDIWhy MongoDB•  Seemed to be mature enough•  Several features matching our requirements§  Dynamic schema§  Fault tolerance and high availability§  Official drivers§  Production support§  Reduced costs•  We did some tests and performed very well06
  19. 19. 19Telefonica DigitalMongoDB-based solution•  We built a new version of the PS with MongoDB 2.0•  Half the team (3 – 4 developers)•  One fourth of the time (4 months)•  We even enhanced some features or added new ones01
  20. 20. 20Telefonica DigitalMongoDB performance•  Performance boost of more than one order of magnitude•  Lower storage requirements (one third)•  Simple, extensible and maintainable schema01MONGODBORACLE
  21. 21. 21Telefonica PDIMongoDB-based solution01
  22. 22. Título del capítuloMáximo 3 líneas05Conclusions
  23. 23. 23Telefonica PDILessons learned•  Awesome performance boost with MongoDB•  Really fast and agile development•  New technology, understand how to use it•  Beat the fear of the unknown. It was mature enough for us•  Great ecosystem & tools, great support•  Lots of new solutions and use cases06
  24. 24. 24Telefonica PDIResults for Telefonica•  Better products performance•  Faster and easier development•  Increased customer satisfaction•  Decreased costs, increased revenue•  Opportunities for new products and services§  Firefox OS push notifications§  Telefonica Machine-to-machine solutions06
  25. 25. Q & AThanks!
  26. 26. How MongoDB Helps Telefonica Digital, Pablo EnfedaqueNext Sessions at 2:505th Floor:West Side Ballroom 3&4: Data Modeling Examples from the Real WorldWest Side Ballroom 1&2: Growing Up MongoDBJuilliard Complex: Business Track: MetLife Leapfrogs Insurance Industrywith MongoDB-Powered Big Data ApplicationLyceum Complex: Ask the Experts: MongoDB Monitoring and BackupService Session7th Floor:Empire Complex: How We Fixed Our MongoDB ProblemsSoHo Complex: High Performance,High Scale MongoDB on AWS: AHands On Guide