TokuMX is a opensource drop-in replacement for MongoDB. It has features like transactions,compression etc which give it a upper hand compared to MongoDB.. Then why isnt TokuMX the default choice ahead of MongoDB?? Has anyone here used TokuMX in production?
MongoDB vs TokuMX - Why shouldnt TokuMX be used by default instead of MongoDB
2.4k Views Asked by vmr At
2
There are 2 best solutions below
2
On
We were evaluating TokuMX some months ago, and the main reason we rejected it was absence of new 2.6 features (it was based on 2.4 mongo engine that time). Additionally, we found that a real compression was pretty far from what is advertised (in our case, of course, your case may be closer to their ideal conditions), and almost no gain in performance. We decided that the game is not worth the candle.
I was drawn towards TokuMX since it gave better performance and had good compression of data but as I went deeper, I found that TokuMX doesn't support text Search and the Mongo engine is v2.4 which was very disappointing. Having said that TokuMX v2.1 seems to support Mongo engine v2.6 but has no mention of text search and the release date is uncertain. Also Note that you get better insert and update performance in TokuMX due to fractal tree indexing but read speed is not much of a difference. Since My application was more to do with read it was pretty straight decision for me to drop TokuMX and move on with Mongo v2.6. Make sure you consider all the points above while selecting TokuMX.