When comparing ArangoDB vs Oracle Database, the Slant community recommends ArangoDB for most people. In the question“What are the best databases to use for Node.js applications?” ArangoDB is ranked 9th while Oracle Database is ranked 13th.
Ranked in these QuestionsQuestion Ranking
Pro Easy cluster setup
Pro Supports joins
Unlike many NoSQL databases, ArangoDB does support joins in AQL queries.
Pro Powerful Java Driver (Sync & Async)
ArangoDB has a very good Java Driver for synchronous and asynchronous. In addition the team there is working on a Spring Data integration.
Pro Transaction save
You can use ACID Transactions for short and small data retrieval and/or modification operations in ArangoDB.
Pro Document and graph-orientend
You can model your data as documents or as a graph - no data model lock-in. You can even combine both models and use them in a single AQL query.
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 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 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.
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.