An alternative distributed document store is RethinkDB which is slowly emerging in the mainstream NoSQL environment. However, it is still very much in its infancy for it to be viable as a stable database for any production use. The general trend in NoSQL approaches is towards providing amalgamation of features and tools, big data integration as well as management simplicity for scalability requirements. Restrictive license often also poses a hurdle for many businesses who are looking to scale out of relational database schema. It seems the door into NoSQL implementation is getting wider and wider with a growing plethora of options, features, and language bindings. But, with such a vast options becomes all the more critical in selecting the right database. RethinkDB is an approach to bind all the good things between Cassandra and CouchDB into one database implementation. It is questionable as to what really one classes as positives for CouchDB. One reason why CouchDB was forked into Couchbase was as a way of harnessing a more stable approach with utilization of Memcache. More often than not, businesses will opt for a MongoDB solution over CouchDB. RethinkDB in time could offer an alternative over MongoDB. There is still a lot that appears to be needed with RethinkDB in terms of native Java support for it to be endorsed into production grade deployments. Also, more use cases of production ready deployments would provide for more community and industry driven insights. RethinkDB, as the name suggests, is a rethink in all things related to document store design philosophy of today and what it can be in the future, without compromising on the good parts.
a comparison of mongodb and rethinkdb with patent data
comparing mongodb and rethinkdb bulk insert performance
rethinkdb vs mongodb
rethinkdb a qualitative review
findthebest
a comparison of mongodb and rethinkdb with patent data
comparing mongodb and rethinkdb bulk insert performance
rethinkdb vs mongodb
rethinkdb a qualitative review
findthebest