RethinkDB vs TokuMX: What are the differences?
Developers describe RethinkDB as "JSON. Scales to multiple machines with very little effort. Open source". RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn. On the other hand, TokuMX is detailed as "A high-performance, concurrent, compressing, drop-in replacement engine for MongoDB". TokuMX is a drop-in replacement for MongoDB, and offers 20X performance improvements, 90% reduction in database size, and support for ACID transactions with MVCC. TokuMX has the same binaries, supports the same drivers, data model, and features of MongoDB, because it shares much of its code with MongoDB.
RethinkDB and TokuMX belong to "Databases" category of the tech stack.
"Powerful query language" is the primary reason why developers consider RethinkDB over the competitors, whereas "When your two-week MongoDB love affair ends, try this" was stated as the key factor in picking TokuMX.
RethinkDB and TokuMX are both open source tools. It seems that RethinkDB with 22.4K GitHub stars and 1.74K forks on GitHub has more adoption than TokuMX with 679 GitHub stars and 90 GitHub forks.
What is RethinkDB?
What is TokuMX?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using RethinkDB?
What are the cons of using TokuMX?
High-speed update-aware storage used in our region server infrastructure; provides a good middle layer for storage of rapidly modified information.
Main database, using it in multiple datacenters in an active-active configuration.