Drizzle - a new direction for databases
Unveiled at the O'Reilly Open Source Convention (OSCON) by Brian Aker (MySQL Director of Architecture), Drizzle can be described as a "what if" project for creating a database specifically tuned for a particular subset of applications.
Brian outlines this best in his blog:
The goal right now is to target a certain class of applications/developers and see if this is useful. As an example:
What are the bigger differences in philosophies?
- Web based apps.
- Cloud components.
- Databases without business logic (aka stored procedures).
- Multi-Core architecture.
Adopt external libraries, use open source mechanics for contributions, keep to an open style of communication, and remove the line between internal and external development. Essentially do what I have been referring to as "Organic Open Source". We have focused on C99, POSIX and autotools based systems. We have taken to a very micro-kernel design where code is being removed from the center and pushed out to the edges via interfaces. We are taking a Linux/Apache tightly coupled design for modules.
More formally, Drizzles features are:
- Based on MySQL 6.0 source tree
- No shipped libraries
- POSIX compliance
- Micro kernel design
- Pluggable Architecture for views, stored procedures, UDFs, storage engines ...
- Sharding across multiple nodes
- Intelligent proxy
- Multi CPU/Multi Core
- Optimized field types
- Efficient memory useage
- No internal ACL, use LDAP/PAM
- No database data formatting
- Cleaned up make system
- InnoDB default storage engine
- Windows compatibility removed
Currently Drizzle is in alpha (with major new changes being introduced daily), with no stable release or binary release. For more information, or to download and experiment, visit the Drizzle website.