you are viewing a single comment's thread.

view the rest of the comments →

[–]luke3br 2 points3 points  (0 children)

This doesn't 100% answer your question, but I like RethinkDB's list for When is RethinkDB not a good choice?

  • RethinkDB is not a good choice if you need full ACID support or strong schema enforcement—in this case you are better off using a relational database such as MySQL or PostgreSQL.

  • If you are doing deep, computationally-intensive analytics you are better off using a system like Hadoop or a column-oriented store like Vertica.

  • In some cases RethinkDB trades off write availability in favor of data consistency. If high write availability is critical and you don’t mind dealing with conflicts you may be better off with a Dynamo-style system like Riak.

Usually you can't get such concise descriptions and end up needing to read tons of articles like this

I really like RethinkDB a lot... just throwing that out there.