RocksDB vs TokuMX: What are the differences?
Developers describe RocksDB as "Embeddable persistent key-value store for fast storage, developed and maintained by Facebook Database Engineering Team". RocksDB is an embeddable persistent key-value store for fast storage. RocksDB can also be the foundation for a client-server database but our current focus is on embedded workloads. RocksDB builds on LevelDB to be scalable to run on servers with many CPU cores, to efficiently use fast storage, to support IO-bound, in-memory and write-once workloads, and to be flexible to allow for innovation. 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.
RocksDB and TokuMX belong to "Databases" category of the tech stack.
"Very fast" is the primary reason why developers consider RocksDB over the competitors, whereas "When your two-week MongoDB love affair ends, try this" was stated as the key factor in picking TokuMX.
RocksDB and TokuMX are both open source tools. It seems that RocksDB with 14.3K GitHub stars and 3.12K forks on GitHub has more adoption than TokuMX with 679 GitHub stars and 90 GitHub forks.
Sign up to add or upvote prosMake informed product decisions
What is RocksDB?
What is TokuMX?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions