When comparing Oracle Database vs Couchbase, the Slant community recommends Couchbase for most people. In the question“What are the best databases to use for Node.js applications?” Couchbase is ranked 14th while Oracle Database is ranked 15th. The most important reason people chose Couchbase is:
Couchbase and Couchbase Mobile are open source and released under the Apache License.
Ranked in these QuestionsQuestion Ranking
Pros
Pro World wide technical support
Oracle is a large company with specialists in a lot of countries. It's very easy to find consultants and any kind of help with Oracle.
Pro Useful features for daily workflow
Some of the most important features are the partitioning option, active data guard, and security options. All of these are very useful for daily workflow.
Pro Stable
Pro Secure
Pro Scalable
Pro Reduced downtime during upgrades
Oracle Database has parallel upgrading for high available applications. Updates are made in parallel without keeping the database down.
Pro High performance parallel quesries
Oracle Database has introduced concurrent execution of union branches, which means that one set of parallel servers will execute one branch, a second set will execute another branch and so on. Instead of the old system where each branch executed one after the other.
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 Proprietary
Con Terrible company reputation
Oracle is very (in)famous for being involved in a number of controversies. Some of them have ended up in lawsuits with other tech companies because of license disputes. The latest one is a lawsuit against Google for Google's implementation of JAVA in their Android ecosystem.
Con Ghost data
To work around ghost data you can after encrypting something, manually move everything out of the old table space and then shred those data files. To be able to get rid of ghost data automatically would be great.
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