Drizzle seeks to scale up MySQL



Email    print   
April 24, 2009 —  (Page 1 of 2)
Brian Aker is rebuilding MySQL in the image of the Apache Web Server. As the director of architecture at MySQL, he's been spending much of his time over the last year studying what it is that developers actually use in MySQL. To that end, he expects to deliver Drizzle, a complete fork of the MySQL codebase, sometime next year.

For now, Drizzle is developing smoothly in four-month windows. “The focus is the restructuring of the code and enabling others to write the features they actually need,” said Aker. That means tossing out most of the typical features, such as authentication and stored procedures, found in a modern database.

Aker said the inspiration for Drizzle came after the MySQL 5.0 release in late 2005, while he was presenting at user conferences. “At the very end of a MySQL 5.0 presentation, there were some different emotions going on in the room," he said.

"Half the room was into 5.0. They were the people who take the SQL and they embed it in the application. They needed a cheaper version of Oracle. The other half of the room said, 'We don't care about your new features, what we care about is, does it perform better? In fact, we want to disable the new features.' "

Thus Drizzle was born with a design from the ground up to emulate the Apache Web Server's plug-in system. That will allow the open-source community to add functionality while Aker and his team focus on speed and scalability.

“We've been working on a new protocol [that] is more centric to the Web environment," said Aker. "All databases today are built around client/server. We need to be able to build stateless and stateless-like protocols to communicate with databases. We'll use UDP [User Datagram Protocol] for fire-and-forget type stuff. And we'll change the protocol to stop things like SQL injection.

“We decided to focus on Web applications. Today, MySQL performs pretty poorly if you go over four cores. The MySQL market is just now entering 16 cores. We had to go back and say, 'How do we make it so in the future we can scale?' The world is 64-bit, and SSD will be common in two years. There's a lot of RAM. Why spend our time trying to make 32-bit work? We needed to make the database much more maintainable. The modular architecture design was a takeaway from Apache. We threw out the concept of one core monolithic codebase.”



Related Search Term(s): Drizzle, MySQL

Pages 1 2 


Share this link: http://sdt.bz/33431
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
MySQL community goes on offensive
MySQL's creator is again trying to rally the community to block the Oracle/Sun acquisition Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

Bloomberg opens its API
Bloomberg's APIs could lead to a future standard for accessing market data.
02/01/2012 04:41 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb