Recommendations to others considering CouchDB:
The problem I see in general is with the word no-sql.
CouchDb is no-sql but so is redis and mongoDb and they are very different.
No-sql offers specific solutions for specific problems. This is different from the SQL world where you solve everything with SQL. People that live with sql typically install their database even before they receive specs.
That being said CouchDB is designed to serve information with speed and redundancy in a scenario where you are mostly reading data. You will also have a limited freedom regarding querying (even if you script). It would be a fantastic DB for a catalog but be wary if you need need heavy updates as it takes some time for data to propagate, or if you need to run reports that have not yet been defined. Review collected by and hosted on G2.com.
What problems is CouchDB solving and how is that benefiting you?
Its fast and simple to develop. Great for startups and prototypes.
You can use it as a very large cache.
You can use it as a versioning system for documents.
By design its awesome for syncing data between apps.
Review collected by and hosted on G2.com.