Search
Follow Us

Follow nosqldatabases on Twitter Follow nosqldatabases on Facebook Follow nosqldatabases on Google Buzz Follow nosqldatabases on LinkedIn Follow nosqldatabases on FeedBurner NoSQL presentations on slideshare

Sponsors

Become a sponsor of NoSQLDatabases.com. Contact us to find out how.

Featured Jobs

 

Follow On Facebook
Recent NoSQL News

Advertisments
« Membase for Dummies: Creating a bucket within Membase | Main | Introduction to Riak »
Thursday
Dec092010

Sharing Life's Joy using MongoDB: A Shutterfly Case Study

The first set of videos from MongoSV are now available online. The first presentation that I'll be breaking down is the Shutterfly case study. This presentation was given by Kenny Gorman a data architect at Shutterfly. This presentation focuses on Shutterfly's usage of MongoDB for photo metadata. The presentation looks at the existing infrastructure, what MongoDB is used for and how they migrated from Oracle to MongoDB.

  • Current metadata was persisted in an Oracle RDBMS (20TB of data)
  • Existing infrastructure was beginning to show its age slowing down development. In addition, infrastructure teetering on the border of needing to spend additional money on licensing costs and specialized hardware to handle increased load.
  • Requiremnents for new infrastructure called for commodity hardware, open source software, horizontal scaling, data locality and low cost
  • Comparison was done between several NoSQL databases, MongoDB obviously won
  • Key features that MongoDB provided: BSON/JSON data formats, replica sets, sharding, commercial support, good community, etc.
  • Project would be need to be phased, use dual writes, more features over time
  • Phased migration of data XML without MongoDB, MongoDB with XML, MongoDB/BSON without XML
  • Hardware configuration is just a standard Intel box (CentOS, 48GB Ram, 3TB RAID 10, Dual Quad Core)
  • Four servers per replica set, backups are done from slaves
  • Data migration was set to be done in two phases. First phase was to treat MongoDB as a cache, upon a cache miss migrate the data and populate MongoDB. Second phase would be to move remaining data to MongoDB
  • Results: 500% improvement in cost, 900% improvement in performance, latency from 400ms to 2ms
  • Lessons learned: protect your writers, good developers make a world of difference, data modeling is still challenging

Watch: Sharing Life's Joy using MongoDB: A Shutterfly Case Study

UPDATE:

Kenny has posted the slides to his blog, I've embedded them here:

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>