Who Is the Drizzle?
So there appears to be a new superhero…uh…super database in town. It’s more “What is the Drizzle” instead of “Who is the Drizzle” and it looks like one of Monty Widenius’ pet projects.
- Drizzle is what MySQL would be with a more interactive community involvement in the design of the software itself, and had targeted website deployments.
- Drizzle is a version of MySQL that is driven by Brian and the community, attempting to solve practical problems that a large group of MySQL users are facing.
- Drizzle is a smaller, slimmer and (hopefully) faster version of MySQL; Features that the broad Drizzle community does not want or need are now removed or in the process of being removed (This includes stored procedures, views, triggers, grants, some non-pluggable storage engines and more).
When me and my buddies get together it’s usually questions like “What if I had a 12″ swanson” and “What if I looked like Brad Pitt” not “What if we ripped out stored procedures out of a database engine” (for the record my friends ask about the 12″ swanson, I just smile).
Stored Procedures, Views, Triggers, Query Cache, and Prepared Statements are gone for now. The field types have been simplified and there is an open debate about the SHOW commands (I am falling into the camp that think they may just belong in the client application but not in the server).
Brian “Krow” Aker’s Idle Thoughts – Drizzle, Clouds, “What If?”
So what kind of applications would be appropriate for such an awesomely slimmed down database engine? I’m glad you asked and here is the clippy:
1) Web based apps.
2) Cloud components.
3) Databases without business logic (aka stored procedures).
4) Multi-Core architecture.Brian “Krow” Aker’s Idle Thoughts – Drizzle, Clouds, “What If?”
Do you have a slick new logo?
Do you have major industry media coverage?
Drizzle can be thought of as a counter-approach to the problems that key/value stores are meant to solve. Drizzle began life as a spin-off of the MySQL (6.0) relational database. Over the last few months, its developers have removed a host of non-core features (including views, triggers, prepared statements, stored procedures, query cache, ACL, and a number of data types), with the aim of creating a leaner, simpler, faster database system. Drizzle can still store relational data; as Brian Aker of MySQL/Sun puts it, “There is no reason to throw out the baby with the bath water.” The aim is to build a semi-relational database platform tailored to web- and cloud-based apps running on systems with 16 cores or more.
How about a slick new website to coordinate all this cool database goodness, oh Heroes of the Rows and Columns?
The Drizzle project is building a database optimized for Cloud and Net applications. It is being designed for massive concurrency on modern multi-cpu/core architecture. The code is originally derived from MySQL.The drizzle project is discussed on the drizzle-discuss mailing list. If you want to show your support for the project, or join the mailing list, sign up here:
https://launchpad. net/~drizzle- discuss/ The project is focused on making a database that is:
1) Reliable
2) Fast and scalable on modern architecture
3) Simply design for ease of installation and management
Jeesus…all that frakkin’ work for a Aqua Teen Hunger Force joke…
April 13th, 2011 at 9:04 pm
[...] clipped some stuff on Drizzle from ReadWriteWeb and that same article mentioned CouchDB in the same list. CouchDB is a free, [...]