Recommendations to others considering CouchDB:
Consider how fast the technologies in your stack change and the impact of these changes. CouchDB is based around common and well-known technologies: HTTP, JSON, Javascript.
When we started with CouchDB, we did not plan on using logstash or Elasticsearch. But we use both now and the integration was trivial. We can use Postman for experimenting and testing. These are just two examples of how easy it was to make CouchDB work with other things - an effort that would have been much harder if CouchDB had a binary interface, or didn't use JSON, or required us to learn a new language to write our m/r functions. Review collected by and hosted on G2.com.
What problems is CouchDB solving and how is that benefiting you?
We are capturing large amounts of unstructured data from hundreds of remote locations and at greatly varying rates. The devices sourcing this data range from IoT (Raspberry Pi) to very large servers. We process around 500GB of new or modified data per hour - CouchDB handles this fine.
CouchDB is also used for simple messaging between systems (using change API). And we use replication to distribute software updates out to remote sites. This provides a simple and "free" reliable mechanism to update many sites automatically.
We use M/R for simple, single-term searches and for summary displays of data (using shows & lists). We use logstash to send data from CouchDB to Elasticsearch for more complex & full-text searches.
Benefits have been numerous: we have scaled horizontally and vertically several times with no issues. Performance of CouchDB is excellent on mediocre hardware. CouchDB has proved to be very reliable and immune to issues caused by bugs or network errors. Review collected by and hosted on G2.com.