One Year with MongoDB

Wordnik recently has surpassed one year in production with MongoDB and they've written about the experience so far. Now we've written about Wordnik in the past but it's always interesting to go back and see how things have evolved.

Click to read more ...

From MySQL to MongoDB at Wordnik

Tony Tam from Wordnik describes their migration from MySQL to MongoDB. So why migrate from MySQL? Inserts on their MyISAMTables had approached 10 seconds an insert. They continued to produce workarounds. However, this led to an increase in system babysitting. Nothing than a fragile system to make those weeknights and weekends extra fun, right?

What are the results?

• Moved 5 Billion rows from MySQL to MongoDB
  • Sustained 100,000 inserts/second
  • Migration tool was the bottleneck (CPU Bound)
• Wordnik now reads from MongoDB very fast
  • Read + create java objects @ 250,000/second

What about the advice of going live with MongoDB?

• Choose your use case carefully if migrating incrementally
• Scary no matter what
• Test your perf monitoring system first!
• Use your DAOs from migration
• Turn on MongoDB on one server, monitor, tune (rollback, repeat)
• Full switch over when comfortable

As a follow-up Wordnik discussed in a post that they are now hosting 9 billion documents. Read more at B is for Billion

Links of the Day - 2010/07/13

Links of the day for July 13, 2010

• B is for Billion - So a couple of weeks ago we had an article about Approaching 1 Billion Documents with MongoDB, well the folks at Wordnik have outdone that nine fold. That's right 9 billion documents. Their public API is serving up 100 million requests a week "without breaking a sweat".
• NoSQL Pioneers Are Driving the Web’s Manifest Destiny - Continuation of the Twitter not pushing Cassandra for tweet storage, this time from GigaOM.
• MongoDB Performance and Durability - Mikeal Rogers from CouchIO offers up this excellent article that examines the performance and durability of MongoDB.