Skip to content


Closing MySQL: Marten Mickos Responds

April 23, 2008

Posted by: Glyn Moody


GM: Does this not undermine the story that you've been telling people over the years about how wonderful open source is because of all these benefits - you're saying well, actually we're not going to use those benefits for some of our code?

MM: Sure, that's of course the worrisome conflict here. And that's why I am saying that we are pragmatists more than dogmatists - meaning if it takes an occasional non-GPL feature to be a successful GPL company, then I'm ready to do so. I absolutely believe in open source and I continue to do so, but the world is not perfect, and until we've figured out the most wonderful business model that works without these things, then we'll experiment with these things.

It's a little bit similar with software patents. We think they should be abolished, but until they are abolished, we need to operate in that world. MySQL actually has some software patents, because we acquired a product some year ago, we got some software patents with it. I'd rather be pragmatic and successful than dogmatic and risking extinction.

GM: Isn't that a tacit admission that the pure open source model isn't really working as well as you'd like it to, and therefore you are being forced to do things which you'd rather not?

MM: It's an admission that open source doesn't solve all business model issues. Like I said, the world is not perfect. A few years from now we may all be operating in the cloud, no software is being delivered anyhow, everything is used as a service, and that actually will be a great business model. Some smart people have suggested - and that's part of our planning - that we should by offering MySQL in the cloud, offering it as a service to people, and when we do that we will be able to be both open source and charge money for the service we provide.

GM: Given that that sounds like a perfect solution, what's stopping you from jumping into the cloud now?

MM: We will be, it's just that the technology isn't ready yet: the complete technology isn't ready yet, customers aren't ready, the infrastructure is not there. You can see it coming, and I think you're seeing it clearly coming with Amazon and others and Sun working on it, [but] it hasn't taken over the world yet.

With backups specifically, which this whole discussion is partly about, there are ideas about providing backup as a cloud service, as a hosted service. So you'd run your database at home, or wherever you are in your office, and you'll push your backups out to the cloud, or to a hosted service, so that you don't need to worry about it.

GM: So is this backup addon a necessary step towards the cloud then?

MM: The addon's not, but the API [is]. Unfortunately everybody's focussing now on the addon and taking that as a sign that the whole world is collapsing, and MySQL is close-sourcing, but they should pay attention to the API, because that's the interesting thing here.

We always had a storage engine API inside MySQL, but when we really opened it, documented it, told people about it, we got an enormous amount of innovation around the storage engine API. This year at the MySQL conference we had five or six storage engine partners, each building their storage engine for MySQL, fantastic innovation, some of them open source, some of them closed source. Nobody yelled or screamed that some of the storage engines are closed source, people are just happy that there's new innovation happening.

And I know MySQL will always be held to a different standard than its partners, but the question that people have asked is, so why is it OK to be a partner of MySQL and have commercial plugins for MySQL, but why cannot MySQL the company do it themselves?

GM: Perhaps the reason is that some people would say you're the most important open source company, and therefore set the example for everyone else to follow?

MM: And that's what I'm saying: I must take it as an honour. Of course we didn't communicate this thing right, we have only ourselves to blame for this coming out the wrong way; but apart from that, we've gone through PR controversies before in our lives, and they can be very painful when they happen, and people think the sky is falling, but many times they lead to very useful outcomes. Because when people really are passionate or upset or angry, they also may come up with some of their best ideas.

Now read

Glyn Moody’s Open Enterprise Interviews

The definitive collection of interviews with the key players in the open source and free software sector.

Jump to page : [ 1 ] [ 2 ]

Follow highlights from ComputerworldUK on Twitter
Sign up for our Daily Newsletter
The UK IT News widget Get it for your site!

<<newer entry | back to blogs indexolder entry>>

Advert

close

Email this article to a friend or colleague:




PLEASE NOTE: Your name is used only to let the recipient know who sent the story, and in case of transmission error. Both your name and the recipient's name and address will not be used for any other purpose.

close
  • This article is now being printed.
close

What are your views on this subject? Use the form below to post a comment on this article up to 1000 characters.


Characters remaining:

close

Click below to add 'Closing MySQL: Marten Mickos Responds' to your blog.



If you do not have a ComputerworldUK Account and would like to use this feature, please Register.

If you are a registered, logged-in user, this will post the title and first paragraph of this story to your blog to share with your readers.

What is this?

Comments received

HanishKVC said on Thursday, 24 April 2008

Hopefully on their own (If not, then because of the community) they have atleast done the right thing of keeping the API open so that others can develop similar solutions. Thanks to SUN and Community for that.
Now is the API going to available to all well in advance or others will come to know it only when MySQL 6 releases ??

Advert

WHITE PAPERS

  • Legal risks: Employee use of the internet and email
    Exploring the challenges facing IT Mangers today and vital steps to ensure safe internet an email use by employees.
  • Phishing for victims
    This White Paper examines the phenomenon of phishing. It explains the potentially catastrophic threat it presents to all kinds of organisation. Exploding some widespread myths, it lights up the murky waters where phishing first emerged and where it continues to evolve. But it also highlights what your business can do to blunt the threat.
  • Challenges and opportunities of PCI
    The control framework implicit in the Payment Card Industry Data Security Standard (PCI DSS) provides an enterprise structure for improving operational, security, and audit performance.
  • Social CRM comes of age
    Who is this “social customer”? What strategies and tools does the new breed of CRM provide to do something about this?
  • Risk Management: Protect and Maximize Stakeholder Value
    What has held organisations back from a broader adoption of risk management programs?
*