Moving from CouchDB to MySQL, or vice versa
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.
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. Hellan on till.klampaeckel.de
CouchDB has some features that other databases don't have: a continuous changes feed, REST interface, master-to-master replication, a web interface to the data and management (Futon).
rdtsc on news.ycombinator.com
document oriented stores are not for every use case, but HTTP REST and JSON are very attractive
Martin on til.klampaeckel.de
Fans of MySQL alternatives
So why did you go back to MySQL instead of moving to PostgreSQL?
Jason on saucelabs.com
We are using InnoDB for more than 8 years – never lose a single bit of data, unplanned downtime is almost zero, this is just unbelievable!
Jack8 on saucelabs.com
Does this story show no development tool is perfect for every application, or that programmers are never satisfied?