|
1900.2.3
by Stewart Smith
fix docs warning: Title underline (and overline) is too short in brief_history_of_drizzle.rst |
1 |
==========================
|
|
1838.2.1
by Brian Aker
More docs. |
2 |
A Brief History Of Drizzle
|
|
1900.2.3
by Stewart Smith
fix docs warning: Title underline (and overline) is too short in brief_history_of_drizzle.rst |
3 |
==========================
|
|
1838.2.1
by Brian Aker
More docs. |
4 |
|
5 |
Drizzle was forked by Brian Aker in 2008 after the Sun Acqusition of MySQL |
|
6 |
by Sun Microsystems. It was announced in 2008 at the O'Reilly Open Source |
|
7 |
Conference. |
|
8 |
||
9 |
Drizzle came into being for both social and technical reasons. |
|
10 |
||
11 |
On the technical side Drizzle is a micro-kernel design that is designed to |
|
12 |
be as pluggable as possible. Anyone should be able to quickly extend the |
|
13 |
database for whatever their needs are. Drizzle has been designed for modern |
|
14 |
architectures and deployments. Drizzle does not shy away from breaking with |
|
15 |
the past, many of the MySQL "Gotchas" have been removed. |
|
16 |
||
17 |
Drizzle is open source software, designed in an organic manner by developers that span different companies. The development process has been geared to one more similar to the Linux Kernel where no single companies owns the source code, or provides all of the developers. In stark difference to MySQL, the goal is to be inclusive as possible and provide stable releases. The social charter of Drizzle encourages diversity and prize respectful dialogue between all participaing parties. |
|
18 |
||
19 |
Drizzle today is the largest fork of the MySQL server. At the time writing, core developers span five companies, with as many, and sometimes more then, 30+ |
|
20 |
developers participating across different contents each month. Drizzle provides every other week releases and is the most well tested database in the MySQL family tree. |
|
21 |
||
22 |
More can be found here http://en.wikipedia.org/wiki/Drizzle_(database_server) |