CouchDB Pros and Cons

Couchdb is a very good platform to learn more about NoSQL as a user can easily create the database simply by clicking in create a database and performing other actions like delete add new doc new view or mango index very easily. Review collected by and hosted on G2.com.

I agree couchdb is good start for a user who is learning the NoSql but for a new user they need practice and may take some time to learn new concepts and understand the complete interface. Review collected by and hosted on G2.com.

helps us implement our application with offline mode, that is crucial to our business. Review collected by and hosted on G2.com.

not a lot of integrations in monitoring. Review collected by and hosted on G2.com.

Too easy, it's very userfriendly and offline first DB. We can simply query by REST API, no need for writing complex queries or installing drivers. Easy Integration with apps Review collected by and hosted on G2.com.

There are some advanced Big Data operations which is tricky to use, and it's difficult to perform complex queries. Performance might be a concern Review collected by and hosted on G2.com.

CouchDB installation process is simple and easy to understand. Perfect Database that Scales quickly Review collected by and hosted on G2.com.

Better documentation is required for the developers Review collected by and hosted on G2.com.

The best thing couch db is its documentation and support.

The documentation is very helpful when you are stuck at something and their support is top notch Review collected by and hosted on G2.com.

Installation process and initial setup could be better Review collected by and hosted on G2.com.

Can run a single logic DB in multiple servers Review collected by and hosted on G2.com.

Structure is not defined clearly from the beginning Review collected by and hosted on G2.com.

Good to use couch db better db fast one use it Review collected by and hosted on G2.com.

Not much as of now as it's going good for now Review collected by and hosted on G2.com.

What I like most about CouchDB is we can host it on our private server. I use CouchDB as part of my client project, and it allows me to store different types of data as a document. It supports rest API calls and provides various features to filter data from databases using API calls. Review collected by and hosted on G2.com.

CouchDB community support is not promising at all. There are not many public response forms to discuss the functionalities. Even in StackOverflow, there is not much response to developers' questions. I feel there is much needed to develop a community like MongoDB. Review collected by and hosted on G2.com.

Since by design Couch DB is made for high availability its enables us to create highly reliable services and a great API provides seamless integration with the rest of the ecosystem.

The replication mechanism is the best and highly configurable so as for different customers different configurations can be enabled. Remote monitoring is also a highlight which helps to diagnose problems in advance and take corrective actions as needed Review collected by and hosted on G2.com.

The general availability of skilled engineers with CouchDB skillset is a persistent problem. This results in a long ramp up for the joined and it takes time for them to develop their skillset and be up to speed Review collected by and hosted on G2.com.

Pros of CouchDB are:-

CouchDB enable replication of itself easily which lead to data sharing among different devices.

CouchDB allow flexible data structure, means any type of data can be stored together.

CouchDB uses HTTP API for easy communication among database.

ReduceMap allow optimize combining of data

Document oriented database management! This alone is worth it: being able to describe your record in a JSON document, and then index it is HUGE.

You're able to store the SAME document in multiple database instances, and due to CouchDB's engine, it is not a problem.

FAST: Accessing JSON is programmatically easy to parse, and therefore makes it to choose

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. Review collected by and hosted on G2.com.

Cons of CouchDB are:-

CouchDB takes extra space for overhead, which is a major disadvantage as compare to other database.

Creating random queries, which do not have any view are expensive.

No built in full text search

Although there are ways: couchdb-lucene, elasticsearch

plus some more:

It doesn't support transactions

It means that enforcing uniqueness of one field across all documents is not safe, for example, enforcing that a username is unique. Another consequence of CouchDB's inability to support the typical notion of a transaction is that things like inc/decrementing a value and saving it back are also dangerous. There aren't many instances that we would want to simply inc/decrement some value where we couldn't just store the individual documents separately and aggregate them with a view.

Relational data

If the data makes a lot of sense to be in 3rd normal form, and we try to follow that form in CouchDB, we are going to run into a lot of trouble. A possible way to solve this problem is with view collations, but we might constantly going to be fighting with the system. If the data can be reformatted to be much more denormalized, then CouchDB will work fine.

Data warehouse

The problem with this is that temporary views in CouchDB on large datasets are really slow. Using CouchDB and permanent views could work quite well. However, in most of cases, a Column-Oriented Database of some sort is a much better tool for the data warehousing job. Review collected by and hosted on G2.com.