Apache CouchDB vs. Apache Druid

Great for REST API development, if you want a small, fast server that will send and receive JSON structures, CouchDB is hard to beat. Not great for enterprise-level relational database querying (no kidding). While by definition, document-oriented databases are not relational, porting or migrating from relational, and using CouchDB as a backend is probably not a wise move as it's reliable, but It may not always be highly available.

Incentivized

It is extremely well suited to rapid ingest of data from large data sources, due to the fact that you can restrict what is ingested by column/field, so that you only pull in the data you actually want or need.

As stated earlier, the open source version could use better cluster management tools, and troubleshooting tools for failing jobs/tasks.

• It can replicate and sync with web browsers via PouchDB. This lets you keep a synced copy of your database on the client-side, which offers much faster data access than continuous HTTP requests would allow, and enables offline usage.
• Simple Map/Reduce support. The M/R system lets you process terabytes of documents in parallel, save the results, and only need to reprocess documents that have changed on subsequent updates. While not as powerful as Hadoop, it is an easy to use query system that's hard to screw up.
• Sharding and Clustering support. As of CouchDB 2.0, it supports clustering and sharding of documents between instances without needing a load balancer to determine where requests should go.
• Master to Master replication lets you clone, continuously backup, and listen for changes through the replication protocol, even over unreliable WAN links.

Incentivized

• Rapid ingest
• Limiting ingest to only the relevant fields/columns
• Easy ingest spec creation

• NoSQL DB can become a challenge for seasoned RDBMS users.
• The map-reduce paradigm can be very demanding for first-time users.
• JSON format documents with Key-Value pairs are somewhat verbose and consume more storage.

Incentivized

• Security configuration is problematic
• Cluster management could have more features
• Troubleshooting incomplete tasks/jobs is a chore

Because our current solution S3 is working great and CouchDB was a nightmare. The worst is that at first, it seemed fine until we filled it with tons of data and then started to create views and actually delete.

Incentivized

Couchdb is very simple to use and the features are also reduced but well implemented. In order to use it the way its designed, the ui is adequate and easy. Of course, there are some other task that can't be performed through the admin ui but the minimalistic design allows you to use external libraries to develop custom scripts

Incentivized

it support is minimal also hw requirements. Also for development, we can have databases replicated everywhere and the replication is automagical. once you set up the security and the rules for replication, you are ready to go. The absence of a model let you build your app the way you want it

Incentivized

It has been 5+ years since we chose CouchDB. We looked an MongoDB, Cassandra, and probably some others. At the end of the day, the performance, power potential, and simplicity of CouchDB made it a simple choice for our needs. No one should use just because we did. As I said early, make sure you understand your problems, and find the right solution. Some random reading that might be useful: http://www.julianbrowne.com/article/viewer/brewers-cap-theorem https://www.couchbase.com/nosql-resources/why-nosql\ https://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed

Incentivized

• It has saved us hours and hours of coding.
• It is has taught us a new way to look at things.
• It has taught us patience as the first few weeks with CouchDB were not pleasant. It was not easy to pick up like MongoDB.

Incentivized

• Integration with S3 storage has saved about 35% on our storage, over HDFS
• The rapid ingest has saved user's time in the query aspects of their applications.
• The ability to ingest from a variety of data sources has made overall user application queries much simpler