Drizzle - Status, Principles and Ecosystem

Drizzle
Status, Principles, and Ecosystem
OSCON
July 2009

Wednesday, July 22, 2009

Agenda
1. Overiew
2. Drizzle Panel Members
3. Question Time


Overview


In the beginning


In a land not too far away


In a land not too far away
(Seattle actually)


One Man
had a vision


of better rain!


of better rain!
(not really)


A database world of an extensible,
pluggable micro kernel


designed for many cores
and to run in the cloud


to be infrastructure aware
and designed for web applications


To ﬁght the tyranny of the
commercial RDBMS world


To enhance the
Open Source community


So!


At OSCON 2008
Drizzle was announced


And Now...
One year on


No kittens have been
harmed in this project


but seriously


The Drizzle Team
• Brian Aker

• Monty Taylor

• Jay Pipes

• Stewart Smith

• Eric Day

• Lee Bieber


Drizzle Contributors
• Mark Atwood • Ronald Bradford
• Patrick Galbraith • Michael Shadle
• Padraig O'Sullivan • David Shrewsbury
• Toru Maesaka • Philip Herron
• Roland Bouman • Sherri Cabral
• Sergey Petrunia • Andrew Ettinger
• Trond Norbye • Clint Byrum
• Nathan Williams • Vladimir Kolesnikov
• Aarti Pai
• Stephane Varoqui and a cast of many more
100+ Contributors

Drizzle Availability
• Drizzle Code: https://launchpad.net/drizzle

• Mailing List: https://launchpad.net/~drizzle-discuss/

• IRC: irc://irc.freenode.net/#drizzle

• Web: http://drizzle.org (Wiki, Docs, Links etc)

• Blogs: http://planetdrizzle.org


Drizzle Projects
https://launchpad.net/libdrizzle
https://launchpad.net/drizzle-automation
https://launchpad.net/drizzle-umbrella
https://launchpad.net/drizzle-interface
https://launchpad.net/drizzle-jdbc
http://pecl.php.net/package/drizzle
https://launchpad.net/drizzle-python
https://launchpad.net/drizzle-cloud
https://launchpad.net/drizzledc
https://launchpad.net/~drizzle-developers
/+archive/ppa
/sysbench and more....

What sets Drizzle apart?
• Reducing active lines of code

• Reuse of existing system libraries (C++/STL)

• Code Coverage / Code documentation

• Regression testing per revision

• Highly extensible via plugins

• Infrastructure aware, focus on web applications

•
Multi Core / High Concurrency / Lots of RAM

What sets Drizzle apart?
Community
• All contributions are treated equally

• No contributor license agreements

• Captain System

• All project information is public

• Release early and often (~ 2 weeks)

• 100+ Contributors / 500+ Mailing List


What is available now?
• Drizzle Server

• Client Library (Supports Drizzle, MySQL, SQL Lite)

• Connectors - Perl DBD:drizzle, php, java, python, ruby, lua?

• Amazon EC2 AMI’s

• Plugins (for example)

• Authentication (PAM,LDAP,Http Auth)

•
Storage Engines - InnoDB, MyISAM, Blitz, PBXT

What is on the roadmap?
• Replication plugins and new protocol

• Pluggable Conﬁguration

• Server Side Scripting

• Performance Schema

• <insert your work here>


More about Drizzle?
• Wiki http://drizzle.org/wiki

• Blogs http://planetdrizzle.org

• Code http://drizzle.org/doxygen/

• Presentations


Audience Poll
• How many of you have tried Drizzle before today?

• How many of you have heard of Drizzle before this conference?


Questions
• Tweet using hashcodes #drizzle #oscon

• Raise your hand


Drizzle Panel Members


Panel Members


Question Time


1. What one feature do you feel sets
Drizzle apart or is unique in open
source development today?


2. Predicting the future,
what will you be saying
at OSCON 2010
about Drizzle?

3.Your Questions Here?


Drizzle - Status, Principles and Ecosystem

Drizzle - Status, Principles and Ecosystem

Recommended

More Related Content

Similar to Drizzle - Status, Principles and Ecosystem

Similar to Drizzle - Status, Principles and Ecosystem(20)

More from Ronald Bradford

More from Ronald Bradford(20)

Recently uploaded

Recently uploaded(20)

Drizzle - Status, Principles and Ecosystem