Brian Aker, MySQL's director of architecture, has unveiled Drizzle, a database project aimed at powering websites with massive concurrency as well as trimming superfluous functionality from MySQL.
Drizzle will have a micro-kernel architecture with code being removed from the Drizzle core and moved through interfaces into modules. Akers has already selected particular functionality for removal: modes, views, triggers, prepared statements, stored procedures, query cache, data conversion inserts, access control lists and some data types.
According to the Drizzle FAQ, the database will be licensed under the GPLv2 and be available on Linux and OS X platforms. Aker stated that he is unwilling to support platforms without a proper GNU toolchain, such as Windows.
"In addition Drizzle will include the latest InnoDB code; You [sic] don't have to wait for MySQL 6.0 or go to the trouble of annually downloading and installing the InnoDB plugin from Oracle just to get access to the latest and fastest InnoDB version", Michael Widenius, MySQL's AB co-founder and original author of MySQL, said in a blog post.
Widenius said that Drizzle was made possible by Sun's acquisition of MySQL and the project had the blessing of Sun's upper management.
No official release schedule has yet been set for Drizzle, but instructions for developers to check out the latest code are available from the Drizzle Wiki.
This was published in 
1
ANJAN BACCHU - 24/07/08
hi there,
"the database will be licensed under the GPLv2 and be available on Linux and OS X platforms."
I thought that mysql would recognize their new masters and support Solaris out of the box going forward ??
BR,
~A
» Report offensive content
2
pete gamache - 24/07/08
@1: Solaris Express is specifically mentioned in the FAQ as a working platform.
» Report offensive content
3
Gr33n3gg - 24/07/08
Uhhh slimmed down, isn't that SQLite....?
http://2500mhz.info
» Report offensive content
4
Don - 24/07/08
Long ago when I first started using Linux, I was going to use PostgreSQL because it had views, triggers etc that MySQL lacked.
But everything I wanted to use worked first on, and was test with, MySQL and all the other things would be available 'soon'.
Now MySQL has a lot of them .. and they are being removed.
Seems its better to be able to run on any database than it is to take advantage of the features the database offers.
» Report offensive content
5
Ilya V. Azarov - 24/07/08
Looks like code crap.
And where is falcon storage? looks like project slowly dies?
» Report offensive content
6
Ayron - 24/07/08
I run a simple database, for simple RADIUS authentication. I don't need all the features provided by MySQL, and it just adds to the bloat on my box, so this is pretty good news.
@Don:
This is a fork, and will not be the "official" MySQL, so the features won't be removed from MySQL, only from Drizzle...
» Report offensive content
7
Gints Plivna - 25/07/08
@Don
Not always more features means better. Every added feature one doesn't use means more code, more possible bugs, possibly slower code, because additional code paths have to be verified. So I think there is niche for such small, fast and feature weak databases.
» Report offensive content
8
Vincent - 25/07/08
Query cache might be useful even if the server is lightweight. Even more if this is a so called "Lightweight SQL Database for Cloud and Web".
» Report offensive content
9
Arjen Lentz - 20/10/08
OurDelta (ourdelta.org) now provides free enhanced builds of MySQL with various useful patches for improved monitoring and performance.
» Report offensive content