Interview with Brian Aker

MySQL's architect speaks out on the future of database storage engines, Amazon's Web services, the next generation of distributed revision control and the economics of creating open source software.

By Don Marti, LinuxWorld.com, 06/13/07

 Start a discussion    Print article

 Comments (1)    Print article

MySQL architect Brian Aker discusses a wide range of issues in an interview with Don Marti, editor of LinuxWorld.

Related links

Brian Aker's home page

Amazon EC2

Amazon S3

Memcached

S3 Engine for MySQL by Mark Atwood

LinuxWorld Conference and Expo: Conference Tracks

Story tools

Sponsored by:

E-Mail article
Print article
Contact author
AIM article	del.icio.us
Reddit	Digg
Stumble	Slashdot It!

When I look at your Web site, I see some pretty unusual storage engines for MySQL. You can use a Web site as back-end storage or even memcached for memory-backed storage. Do those engines have any practical application? Or are they more in the nature of sample code?

Well, they actually have quite a bit of practical application. In the database industry, we’ve been hearing, especially from companies like IBM, for some time now, about federating sources of data. So, taking data from different sites or, in this case, just different data strategies and putting them together. This is kind of a very early concept that Monty Widenius had when he first came up with MySQL, though it was more around analytics and transactional engines. What we’ve done is we’ve kind of spread that concept out.

The HTTP engine is an interesting one to look at. It was written as a piece of sample code, designed so that it can communicate with a Web site. It can fetch basic data through HTTP methods and then translate that to being able to use as SQL. OK. So what’s the big deal? Well, one big deal of this has been the S3 engine by Mark Atwood. Here’s an engine where you’ve got Amazon, who’s got this large infrastructure of available storage, and what Mark has done is he’s made that available through an engine.

For instance, I know one of his early cases right now is they’ve got a real estate agency that is collecting ongoing statistics and data about sales. And instead of creating a local repository of terabytes or petabytes of data storage, they’ve started architecting it to just like normal SQL. They insert it into their database. But instead of having to store that data locally, it’s actually placed into S3 for long-term archival. So they can take a data set that they may not really need access to all that often and put it into an environment where they don’t have to pay for anything but the actual storage costs. Which, when you work out the numbers between storing that data locally, having more sysadmins, having more infrastructure or just storing it in S3, the numbers are kind of strong toward using the S3 servers.

Featured White Papers

• Hey, Can I Borrow Your Keys? I'd Like to Trash the Kingdom