When comparing CouchDB vs Couchbase, the Slant community recommends CouchDB for most people. In the question“What are the best databases to use for Node.js applications?” CouchDB is ranked 3rd while Couchbase is ranked 14th. The most important reason people chose CouchDB is:
CouchDB works very well even when the network is physically partitioned
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Works well between physical network partitions
CouchDB works very well even when the network is physically partitioned
Pro Available
CouchDB is considered an available DMS according to the ACP theory of database management. As such it allows every client to always read and write
Pro Useful for applications where versioning is important
CouchDB is mostly used in applications where a large amount of data needs to be accumulated and where data only changes rarely.
Pro Changes API
You can use the RESTful API to listen for changes in your database, which is something most databases can't do. It makes it really easy for clients to keep their view of data up-to-date.
Pro RESTful API
Since everything is stored as a JSON document and served over HTTP, it's perfectly suited for communicating with client-side javascript, with or without middleware.
Pro Open source
Couchbase and Couchbase Mobile are open source and released under the Apache License.
Pro Easy to implement N1QL queries
Pro Ability to run ad-hoc SQL like queries on realtime big data
Couchbase N1QL allows native SQL processing over JSON data with high performance indexing for low latency queries at scale.
Pro Easy sync protocol to mobile devices
The minimal code needed to pull data down to a device
Pro Available on Windows, Linux & macOS
Pro Ability to make predefined fast queries
With Couchbase you can make "Views" of data, which are practically predefined queries which are fetched with an O(1) algorithm.
Cons
Con Can only achieve consistency through replication and verification
Since CouchDB is considered an AP (Available, Partition-Tolerant database management system), it is not really consistent (not all clients can have the same view of the data consistently) and the only way to achieve some "eventual consistency" is through replication and verification of data.
Con Uncertain future
After a very promising start, development began to drag after major supporters like Canonical, Selenium and CouchOne either shut down or moved to other tools. Development has begun to pick up again.
Con Vendor lock-in
Con No model mapper for Android
Couchbase does not have a model mapper for Android built-in and out of the box, instead you will have to write your own from scratch.
Con Not Compatible with couchdb
Since version 2 the sync-protocol is no longer compatible with couchdb. This makes couchbase nearly worthless
