Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing RethinkDB vs OrientDB, the Slant community recommends RethinkDB for most people. In the question“What are the best databases to use for Node.js applications?” RethinkDB is ranked 2nd while OrientDB is ranked 10th. The most important reason people chose RethinkDB is:
Only takes about 30 seconds to install. They also have a docker file for running it on AWS, Google Cloud or your own.
Specs
Question Ranking
Pros
Pro Easy install
Only takes about 30 seconds to install. They also have a docker file for running it on AWS, Google Cloud or your own.
Pro Changefeeds (change listeners)
You can listen to changes and trigger code based on these changes.
Pro Powerful query language
RethinkDB's ReQL is a very powerful functional query language. The functional aspects of ReQL and the straightforward implementation of the Node driver for Rethinkdb make it a natural fit for Javascript developers. You no longer have to type some obscure syntax in quotes (aka SQL), your queries are just "natural" Javascript functions in the same way you would use lodash to handle your collections.
Pro Auto master promotion
Unlike a lot of other databases where if the master is down the system is down, this one if the master is down someone else is made master so much more peer to peer.
Pro CLI and web administration tools
RethinkDB has administration tools in both CLI and GUI (web app). You can view whats going on right away by going to localhost:8080. The data explorer allows you to run queries on the db.
Pro Horizontal scalability
RethinkDB is scalable horizontally. It has support for sharding, parallel queries and MVCC concurrency.
Pro Ease of cluster setup
You can directly tell it to shard/replicate and how many shards/replicas depending on the amount of nodes. Each node doesn't need anything except one other node's ip/port in the cluster to join and maybe the auth.
Pro Multi-model database (document, object, graph)
This database is primarily, or historically, thought of as a graph database. However, it is actually a multi-model database that supports a variety of noSQL models (key-value, document, etc.).
Pro Open Source commercial friendly license (Apache 2)
The Apache 2 license is one of the most liberal licenses. You can use OrientDB for any purpose for free.
Pro Free clustering support
Unlike other NoSql databases, OrientDB offers clustering support for free. Furthermore, it's not a basic Master/Slave, but it supports Master-Master replication + Sharding.
Pro Distributed Graph Database with relational type Documents
Pro Supports sql as well as other query languages
It can be queried in a number of ways, but the ability to query with SQL makes it a bit more familiar to use.
Pro Multi-master replication
OrientDB is incredibly scalable thanks to its multi-master replication. All nodes in a cluster can both read and write.
Pro Full text search
Full text search support is available when using Lucene based indexing algorithm.
Pro Performance
OrientDB is very fast, especially when it comes to relationships between records (or "links").
Pro Enterprise version available
The Community Edition is free and covers many features, but an Enterprise Edition is available (prices are transparent, published online) with 24x7 support.
Cons
Con Cannot run queries from its CLI
Con No user accounts
This is just the database, you need to setup your own auth and user accounts (such as using Auth0).
Con Not well known
It's a very unfortunate thing, but it's true. Not many people know of this gem so that makes it difficult to find community support at times. It also makes it hard to get people on board with it who shop products by brand name or flashy marketing. It also means there are fewer code snippets, libraries, and frameworks that consider it. While it's interoperability is good with SQL support and Tinkerpop, it still doesn't change the fact that many things don't give it much thought and that can lead to more work as a developer sometimes.
Con Learning curve
A lot of effort went into making OrientDB easy and familiar to use (such as SQL queries for example). However, it's important to understand the database engine a bit and how it works in general (links for example). This involves a bit of a learning curve if you're not familiar with graph databases. Not an enormous curve or anything, but it's still a consideration.
Con Bulk inserts may cause an out of memory crash
When doing inserts in OrientDB you have to be careful to do them one at a time. Bulk inserts may cause out of memory error.
