Are there any documented projects where CouchDB was tried and rejected?

Question

I keep seeing references to the idea that "CouchDB may not be the best tool in every situation." This is good to know, but unfortunately also applies to every technology.

What would be much more helpful is a description of how CouchDB was tried on a project and subsequently abandoned for a traditional SQL database.

If you've tried CouchDB on a project and later gone back to a SQL database, what factors played the biggest role?

Answer 1

You might want to check out the following articles, which describe a few examples:

• Why CouchDB Sucks
• Stack Overflow - When to use CouchDB vs RDBMS
• When to use CouchDB, when not to...
• Top 10 Reasons to Avoid the SimpleDB Hype
• Does CouchDB supports referential integrity?

Answer 2

There’s a good CouchDB post-mortem from Sauce Labs here:

• http://sauceio.com/index.php/2012/05/goodbye-couchdb/

And another from Signal here:

• http://blog.signalhq.com/2012/01/24/getting-off-the-couchdb/

Answer 3

Its marketing slogans "Relax, it's easy" and "CouchDB bult for the Web" - it's not true.

Because:

1. It's not easy. Ha-ha, writing map/reduce for every query is easy, really? Did someone who advocates it actually tried this approach, on something real I mean, not just two-weekends-blog app?
2. Some common web-app tasks is hard to do with CouchDB (try to get Post with its Comments Count in one query or Tag Cloud (top N tags, not just counts of tags) to see it for Yourself.

So, CouchDB has very interesting and unique features, but its marketing is wrong. It's not for a general web app, it's a nice but a very specialized tool.

P.S. More details http://alex-craft.com/blog/2013/a-little-about-cochudb-and-comparison-with-mongodb

Answer 4

you might find this page useful http://www.mongodb.org/display/DOCS/Comparing+Mongo+DB+and+Couch+DB