Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Cloudant vs Couchbase, the Slant community recommends Cloudant for most people. In the question“What are the best databases for building social network like apps?” Cloudant is ranked 6th while Couchbase is ranked 8th. The most important reason people chose Cloudant is:
You can choose to host your database on a single cloud provider or you can replicate it over several different providers.
Question Ranking
Pros
Pro Can replicate the database across several hosts
You can choose to host your database on a single cloud provider or you can replicate it over several different providers.
Pro Runs on both bare-metal and virtual machine
Users can choose whether their database instance will run on bare-metal or a virtual machine
Pro Crash friendly
The database behind Cloudant, CouchDB uses an append-only file for it's data. To restore already used up space, a compaction must happen. When this happens is up to the database maintainer.
Pro Cloud agnostic
Cloudant hosts databases with a lot of different cloud hosting providers including Amazon, Rackspace, SoftLayer and Microsoft Azure. This way customers can choose where their database is hosted.
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 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
