RethinkDB vs ConcourseDB

Only takes about 30 seconds to install. They also have a docker file for running it on AWS, Google Cloud or your own.

You can listen to changes and trigger code based on these changes.

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.

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.

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.

RethinkDB is scalable horizontally. It has support for sharding, parallel queries and MVCC concurrency.

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.

Concourse tracks versions of your data by default. This way you can easily edit data without being afraid of losing anything since Concourse can easily revert to a previous state.

ConcourseDB is known to have a very holistic approach to robustness and data integrity which is reflected by it being fully ACID compliant.

ConcourseDB has always been strict about making sure data is valid before allowing it into the database, and there is no way for a client to bypass those checks.

Because of its powerful version control capabilities, Concourse can easily and painlessly query and get data from any point in the past.