When comparing Oracle Database vs MongoDB, the Slant community recommends MongoDB for most people. In the question“What are the best databases to use for Node.js applications?” MongoDB is ranked 5th while Oracle Database is ranked 15th. The most important reason people chose MongoDB is:
Miles above other databases in educational resources.
Specs
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 Perfect documentation and tutorials
Miles above other databases in educational resources.
Pro Great speed
MongoDB queries can be very fast because the data is usually all in one place and can easily be retrieved in a single lookup. But this is true only when the data is truly a document. When it's trying to emulate a relational model it starts to become really slow because it may have to perform many independent queries to retrieve a single document.
Pro Uses JSON
As Node.js uses JavaScript there's no need to map the returned JSON data from MongoDB, as JavaScript is a superset of JSON. Essentially solving object-relational impedance mismatch by its very nature. Working with JSON is also easier overall as it more easily fits into how you would represent data on the client.
Pro Doesn't require a unified data structure
Mongo is very flexible in that it doesn't require a unified data structure across all objects. So it's rather easy to use.
Pro Easy to scale
MongoDB has powerful sharding and scaling capabilities for when the data stored in the database gets so large that a single machine may not be able to store all of it. Sharding solves this problem through horizontal scaling. Mongo gives developers the ability to easily and painlessly add or remove as many machines as needed.
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 Reported to lose or corrupt data
MongoDB is famously known for leaking and losing data over time.
Con Document Stores may be not suited for relational data
MongoDB has no JOIN, all relations are supposed to be resolved client-size which entails additional requests to the server.
Con Need many search features
Though it is possible to index and search text in documents in MongoDB 4.0 in multiple languages. The indexing and search is not as powerful as for example Elastic Search. For instance not being able to search for only parts of words.