Re:Vitess: Scaling MySQL databases for the web
by dkhenry on Tuesday February 28, 2012 @10:28PM
(#3646281)
What I don't understand is why you would use MySQL as your storage engine it seems to me you are stripping away most of the benefits of using MySQL by interfacing it with this library. Is there a compelling reason to not use google's own LevelDB?
[ Parent
| on HN ]
Re:Vitess: Scaling MySQL databases for the web
by mattyb on Tuesday February 28, 2012 @11:19PM
(#3646421)
Is there a compelling reason to not use google's own LevelDB?
LevelDB is a key-value storage library. MySQL is a relational database server. They are about as different as data stores can get.
Re:Vitess: Scaling MySQL databases for the web
by stevencorona on Tuesday February 28, 2012 @11:20PM
(#3646426)
Don't really see what parts of mySQL you are stripping away by using this library. It's just extending/improving some weak spots of mySQL- you literally don't lose any features.
Re:Vitess: Scaling MySQL databases for the web
by dkhenry on Wednesday February 29, 2012 @09:03AM
(#3647794)
According to their website -
"""
The way we plan to achieve this is by providing a subset SQL front end with limited guarantees
"""
If your making something to parse and validate SQL yourself which is what it seems like they are doing then why go through all the hassle to run it a second time through another SQL parser. Also since your mandating everything have a "Key" why are we not using a "Key-Value" store.
I am not saying this is a bad project or a bad design decision I am just curious why they made those decisions since at first glance it makes no sense whatsoever.