When is porting data from MySQL to CouchDB NOT advisable? Seeking cautionary tales

Posted by dan on Stack Overflow See other posts from Stack Overflow or by dan
Published on 2011-01-15T00:28:33Z Indexed on 2011/01/15 0:53 UTC
Read the original article Hit count: 204

Filed under:
|
|
|

I've dabbled in CouchDB and I have pretty good MySQL experience. I've also created one production application that uses both. I like MySQL but I've run into scaling/concurrency issues with MySQL that CouchDB advertises itself as a general solution for.

The problem is that I have MySQL based applications that are pretty huge, and I don't really know whether it would be a good idea or not to try to port them over to a CouchDB datastore. I don't want to put in a lot of time and effort only to find out that my application is really not a good fit for CouchDB.

Is there any sort of informed consensus on when porting a MySQL based app to CouchDB is NOT advisable? Any cautionary tales?

I think CouchDB is really cool and want to use it more. I'd also like to know ahead of time what specific types of data querying scenarios CouchDB is really not good for, or if CouchDB can really replace MySQL for all the applications I create going forward.

© Stack Overflow or respective owner

Related posts about mysql

Related posts about database