Slashdot Mirror

MySQLs handlersocket (included since 5.5) does NoSQL-style read and write operations bypassing the SQL engine. While it has some limitations, it will do >200,000 queries/sec on a low-spec server and there are benchmarks of it doing >750,000 on a 8-core Nehalem (faster than Memcached!), and it's not restricted to in-memory operations. The nice thing is that you can use that for the simpler parts of your app, then use transactional SQL on the same database for more complex operations.

Another one to look at is TokuTek's TokuDB, another InnoDB drop-in replacement, which is particularly good for inserts, low disk use and low-latency replication. They ran a demo doing 1 billion indexed inserts in 7 hours when InnoDB took a week.

For distributed 'cloudy' apps, one of the better choices is Drizzle, which retains the nice bits of MySQL (and MySQL client compatibility) and rewrites all the rest.

I don't think I'll believe MemSQL until Percona have benchmarked it...

Take a look at MariaDB and Drizzle.

http://mariadb.org/
http://www.drizzle.org/

Its already forked :)
http://mariadb.org/

And to http://www.drizzle.org/

and Percona: http://www.percona.com/software/percona-server/

>>
>>Its already forked :) http://mariadb.org/
>>
>
>And to http://www.drizzle.org/
>

Call me when drizzle runs on something besides Linux.

Its already forked :) http://mariadb.org/

And to http://www.drizzle.org/

I seem to remember that many years ago, before Sun bought MySQL AB, the license for the library needed to access the database from your own programs was GPL (not LGPL), and MySQL AB claimed you couldn't use it without open-sourcing your code, unless you paid them for a commercial-use license. Has that changed with Drizzle (i.e., have they written a new API so they can choose a different license)? Their license page says:

Drizzle is licensed under both the GPLv2 and BSD license. The core of Drizzle was forked from MySQL and thus is under GPLv2. Derived work from GPLv2 code will stay GPLv2, as the license states...

which doesn't give any detail about which parts are still GPL and which parts are now BSD.

hardely, "many". Drizzle and mariaDB are only two prongs. Maria is really supposed to be CentOS to Oracle's Redhat

Drizzle for the small-scale systems.

Really? Their FAQ says

Can I run a website with this?
No. We are still making incompatible changes, and certainly do not believe the code is production quality. Right now we are defaulting many configure operations to generate debugging code for us so our binaries are not optimal.

support one of the official forks.

official fork sounds paradoxical. What should we call a fork whose only reason for being is to keep something free? Let's call it a frork. Or in the case of Maria and L'Office, a frorakle.

It's not like anybody would ever think of such a thing.

And another in the wings as drizzle - a fork of mysql. This is getting a lot of attention and some parts are considerably cleaner and faster than mysql.

Don't forget OurDelta - http://ourdelta.org/ - [about] "OurDelta produces enhanced builds for MySQL 5.0 and builds for MariaDB 5.1, on common production platforms. James Purser of Open Source On The Air describes OurDelta as “a new distribution for MySQL”."

And then there's the under devellopment Drizzle - http://drizzle.org/ - MySQL rewritten from scratch by (amongst others) Brian Aker.