Moving from CouchDB to MySQL, or vice versa

By , ITworld |  Software, CouchDB, MySQL

Sauce Labs decided they needed to dump CouchDB and move to MySQL. Two years ago, a different blog detailed how and why to move from MySQL to CouchDB.

It all depends on what you need for your application. If you go the wrong direction at the start, or your app needs change, moving from one platform to another becomes necessary. Sauce Labs looked to get away from MySQL and embraced CouchDB back in 2008. But performance and maintenance issues dogged them, so they made the jump to MySQL.

Till Klampaeckel, on his blog, wrote a two part series going the other direction. CouchDB comes with most Linux and Unix distributions. Easy interfacing with PHP makes it handy for website use, and CouchDB offers document-oriented management and storage without schemas.

MySQL fans

We almost made the mistake of using CouchDB at the beginning, we dodged the bullet right off the start and used MySQL.
Mike Curry on suacelabs.com

A properly normalized and "constrained" database prevents data loss from stupid mistakes.
johnbender on news.ycombinator.com

CouchDB fans

When we decided on CouchDB, the decision was heavily influenced by the native map reduce views. Being a xoogler, I was used to map reduce and the calculation needs when computing shopper profiles is very suited to map reduce.
Kunt O.

Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Answers - Powered by ITworld

ITworld Answers helps you solve problems and share expertise. Ask a question or take a crack at answering the new questions below.

Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Ask a Question
randomness