Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

tokutek.com

Post reply on HN
Print view View original

11–20 of 35 posts

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#11

Post by coffeemug »

kbd wrote: post #4

I'd love to hear any opinions the RethinkDB guys have about this.

slava @ rethink here.

I have a few thoughts on this:

a) There is an astronomical difference between a neat technology and a complete, usable, supported product (especially with really complex software like databases). I can't tell yet how committed Toku folks are to this project. Is this a research project that may or may not go somewhere, or are they all in on the product? I think it's very important (for the customers and the industry) to get a clarification on this point.

b) I love seeing engineering projects like these. Experimentation like this (using a superb storage engine to power a popular db) is really exciting. I'd love to see where this goes.

c) RethinkDB has its own state of the art storage engine (with a very different architecture from Toku) that's tightly integrated into the full system. That lets us do very interesting things (fast path code paths, btree-aware caching system, etc.) The advantages and disadvantages of pluggable storage engines are really interesting.

d) If TokuMX does turn into a complete product, it's really exciting. It's nice to see the industry maturing.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#12

Post by leif »

ggoodale wrote: post #8
leif wrote: post #7

Earlier quoted context omitted.

The simplest list is this: no full text search, geo indexes, or background indexing yet.

Is there a feature roadmap somewhere detailing what order these and other features will be added (actual schedule is great too!)?

We're working on that, and we are hoping to base it on feedback, so if there's something you want, definitely let us know.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#14

Post by HarrisonFisk »

This really reminds me a lot of the progression of MySQL.

Originally it was used with ISAM/MyISAM and it was pretty popular. Then InnoDB came around and it quickly revolutionized the MySQL world, allowing MySQL to grow to the next level. Now InnoDB is by far the most commonly used storage engine and the default on several distributions.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#15

Post by mrkurt »

cheald wrote: post #13

Can I put a TokuMX node into a Mongo 2.4 replica set cluster? It would be nice to let it sync to the cluster and then compare it against live Mongo nodes. Any concerns with sharding?

You can't have mixed replica sets, sadly.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#16

Post by esmet »

ggoodale wrote: post #9

What's the storage multiplier for TokuMX vs. straight mongodb? Will my total size on disk go up or down?

Most users should expect a big reduction in disk space. Depending on your data and level of fragmentation with regular MongoDB, you could see ~4x-20x reduced disk usage.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#17

Post by zardosht »

coffeemug wrote: post #11
kbd wrote: post #4

I'd love to hear any opinions the RethinkDB guys have about this.

slava @ rethink here. I have a few thoughts on this: a) There is an astronomical difference between a neat technology and a complete, usable, supported product (especially with really complex software like databases). I can't tell yet how committed Toku folks are to this project. Is this a research project that may or may not go somewhere, or are they all in on the product? I think it's very important (for the custom…

I work for Tokutek. Slava, thanks for the kind words. Just to clear up any possible confusion, this is the product. We release and support TokuMX. The research started roughly a year ago (the blog posts we've done are out there), and it has led to this.

We consider this to be full featured in the sense that we have a feature set that we feel users can deploy in production. As with any product, as users give feedback on what more they would like to see, be it existing MongoDB features or something else, we will use that feedback to enhance the product.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#18

Post by mattparlane »

This is pretty exciting. A couple of questions:

How are you (Tokutek) planning to keep up to date with the MongoDB tree?

Are you planning on talking to the MongoDB folks about upstreaming this? Or will it be a pure fork with no sharing either way?

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#19

Post by esmet »

coffeemug wrote: post #11
kbd wrote: post #4

I'd love to hear any opinions the RethinkDB guys have about this.

slava @ rethink here. I have a few thoughts on this: a) There is an astronomical difference between a neat technology and a complete, usable, supported product (especially with really complex software like databases). I can't tell yet how committed Toku folks are to this project. Is this a research project that may or may not go somewhere, or are they all in on the product? I think it's very important (for the custom…

TokuMX is indeed a complete product, not an experiment. We're proud of it and ready to support it yesterday :)

I completely agree that pluggable storage engines are an interesting topic. But we went the integrated route (ie: no storage API) probably for the same reason: things get simpler and easier to implement when the stack is shorter.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#20

Post by leif »

leif wrote: post #5
anonymous1983 wrote: post #3

Here are a few questions: 1. Is this a drop in replacement if I'm on Mongo 2.4? 2. If I want to migrate back to Mongodb from TokuMX, what needs to be done? 3. How quickly does TokuMX integrate improvements from MongoDB? 4. Is anyone using this in their production deployment?

1. Yep 2. Dump and reload to get between mongodb and TokuMX. The storage systems and replication systems are incompatible

Wow sorry responding on my phone is hard. It's drop in if you're on 2.2. We do not have some 2.4 features (FTS, geo).
Post reply on HN