New RDBMS called 'Drizzle'

Classic Servoy
1

Yesterday Brian Aker announced a fork of MySQL, called Drizzle.
Drizzle is a slimmed-down version of MySQL. No stored procedures. No query cache. No views. No dual license but GPL-only.
It’s goal is to target web bases apps, cloud components, databases without business logic (stored procedures) and multi-core architecture.
It’s appearantly backed up by a lot of the most serious MySQL developers inside and outside of Sun/MySQL. So a very exciting development :) .

However it’s not available yet. To quote from Brians Blog:

Can you download it and use it?

Nope.

Not there yet, and we do not have a target date of when we will be ready for production use. If you want to work on this right now you are going to have to roll up your sleeves (hint, “bzr branch lp:drizzle”). I would really encourage you to go read the mailing list (http://launchpad.net/drizzle). Keep an open mind. We are not looking to be 100% compatible with MySQL, so this is certainly not a replacement for MySQL.

2

Some dumb q’s, maybe:

  1. Does (will) it work with popular storage engines?

  2. Is the main advantage intended to be performance? (which makes me wonder about the absence of a query cache?)

  3. If the answer to 2 is “no” then what is the goal of the serious coders?

thanks, Robert, or whoever answers,

kazar

3

Hi Ilyse,

kazar:

  1. Does (will) it work with popular storage engines?

  2. Is the main advantage intended to be performance? (which makes me wonder about the absence of a query cache?)

  3. If the answer to 2 is “no” then what is the goal of the serious coders?

The Drizzle FAQ does answer some of your questions or gives your a sense of what direction they’re heading.

Here are some quotes of that FAQ:

  • So what are the differences between is and MySQL?

No modes, views, triggers, prepared statements, stored procedures, query cache,
data conversion inserts, ACL. Fewer data types. Less engines, less code.
Assume the primary engine is transactional.

And

  • What is the target?

Deliver a microkernel that we can use to build a database that meets the
needs of a web/cloud infrastructure. To this end we are exploring http
interfaces, sharding enhancements, etc… do not expect an Oracle, MySQL, Postgres, or DB2.

[snip]

We are focusing on multi-core architecture. This is not designed to run on a
wrist watch (hint, go use SQLite). We support both 32bit and 64bit but the
class of machine we are targetting is 64bit. We are making design decisions
which assume very large amounts of RAM will be made available to the DB.

Hope this helps.

4

And in the following podcast Brian Aker gets interviewed and gives much more detailed info, also about why not using a query cache and more.

http://www.linuxworld.com/podcasts/linu … xcast.html

Hope this helps.

5

thanks for the resources, Robert. Will be interesting to watch. For Servoy applciations where logic/procedures/triggers/constraints can be handled within one’s solution, might be nice to have a lean & mean version of MySQL (so long as the solution’s not transactional)

kazar