November 22, 2009
I’m home from UDS-Lucid, and it was a heck of a week. I’m still digesting a lot of session material and a lot of Texas-style BBQ.
It’s nice to come home to the house we bought last month and see familiar things like our front door; and next to it the illuminated sign with our house’s street number.
You will know synchronicity.
October 29, 2009
In what is sure to the the most exciting release announcement of the day (ahem), Monty Program and the MariaDB community are happy to announce the immediate availability of a (mostly?) stable beta release of MariaDB 5.1!
This is a beta. It may well have undiscovered bugs or features that are not fully baked. But the expectation is that we have fixed most of the issues like these, and so we’re looking to the broader community to help us get to a state where we can offer a Release Candidate. So start hammering on MariaDB, and be sure to report any bugs.
If you’re curious as to what we have baked into MariaDB 5.1, and what differentiates us from our upstream project, be sure to look over our guide to MariaDB vs. MySQL®.
If you want to dive right in, you can find source and binary tarballs on the MariaDB download page. And before you ask, yes, we are working on Debian and Red Hat packages. It’s a high priority.
Now, GO! Download and help us polish up an RC!
September 3, 2009
Today the European Commission expressed their concern about Oracle’s acquisition of Sun, framed in the context of the database market.
What strikes me as particularly funny in the reportage on this story is many analysts’ claims that MySQL has a small market share. I’ll pick on Gartner here:
“MySQL has extremely small market share,” said Andy Butler, an analyst with IT research firm Gartner. “The E.C. is losing sight of the big picture and is bringing about a more anticompetitive situation by focusing on one product at the expense of the other moving parts.”
This quote is pulled from a Wall Street Journal article that posits, “Many analysts believe the commission’s focus on MySQL is misplaced. MySQL’s share of the $19 billion global database market is approximately 1.5%. It is dwarfed not only by Oracle’s database business, but by those of competitors such as International Business Machines Corp. (IBM) and Microsoft Corp. (MSFT).”
Gartner and the WSJ are looking at the US$19 billion global database marketplace. That’s an interesting approach, given that the vast majority of MySQL users don’t pay a cent for their software. So their usage does not factor into this US$19 billion market at all.
Now, an Oracle 11g license is not cheap. Every license Oracle sells is a major bite out of the US$19 billion global database market. Every user of the MySQL Community Edition doesn’t even make a nibble.
Forrester Research published a study in 2008 that showed that “MySQL has the highest adoption and growth. MySQL continues to have the largest mindshare in the open source database market and has the highest number of paying customers for product support: an estimated 16,000.”
Gartner themselves, Evans Data Corporation, and other industry groups have released similar findings; findings that MySQL and Sun proudly annouce. Indeed, look at the quote at the bottom of that page:
“The future of the database market will be the standardization on MySQL.” – Charlie Garry, Meta Group
Here’s a little informal, unscientific data. Look at Google Trends’ output for MySQL, Oracle 11g, Postgres, db2, and Microsoft SQL Server. It’s quite clear that Google is finding far, FAR more interest MySQL than for any other product among their searches. If MySQL’s market share is so low, why do Google search users search for that term so much more frequently (factor in the tens, if not hundreds, of times)?
With all due respect, I’d suggest Mr. Butler at Gartner read his own company’s reports, and when considering the “global database market,” do so without the blinders of capitalization. The world of business is far more nuanced than can be accurately expressed with a dollar sign in front of one’s research.
August 14, 2009
In July several Monty Program employees attended the Community Leadership Summit and O’Reilly’s Open Source Convention (OSCON), myself included. While there we spoke to developers, partners, users, and interested bystanders of a number of SQL servers: MariaDB, MySQL, Postgres, and others.
The week started with the Community Leadership Summit. First, a big thank you to Jono Bacon for organizing a fantastic unconference, and allowing us to participate! Monty Program considers it our privilege to have helped to sponsor the event, and we look forward to attending and sponsoring it again in the future.
Being an unconference, the schedule is determined by the attendees. We scheduled a session entitled “What’s going on with MySQL?” to answer community questions about the possible future of the MySQL community. The session was very well atttended, with DBAs, developers, Sun employees, and Monty Program execs all in attendance. Also present was Bruce Perens, creator of the Open Source Definition, and Larry Rosen, author of the Open Software License and Academic Free License. To us, this was illustrative of the great interest by many community members in seeing the path Oracle chooses to take with MySQL in the future. Topics included possible scenarios, disaster planning for worst case scenarios, and best practices given Oracle’s relative silence with regards to their plans for MySQL (a topic addressed by Monty in a blog post earlier in July).
A video snippet of the session is available at Wikimedia. Have a look! (Requires a browser plugin capable of Theora playback)
On Sunday night the Postgres team had a release party for Postgres 8.4. Congratulations to the entire Postgres team! It’s a fantastic SQL server, and 8.4 has an impressive list of improvements. Monty and I were invited to the party, and we had a great time. There was a t-shirt auction, and Monty bought the t-shirt off Josh Berkus’ back. Trust me, you haven’t lived until you have seen Josh bare-chested, and a semi-inebriated Finnish hacker having nasal sex with his t-shirt. Classic. Thanks to the Postgres team for a really fun evening!
Postgres vs MySQL? The flame-war is a myth. Grow up.
There was a concerted attempt to recover for Monday morning, and the beginning of OSCON. It’s the premier open source conference, and we were delighted to have been invited to speak. Our talk was on Thursday, and was again well attended.
We divided our talk into three parts. First, I gave an overview of what MariaDB is, how the project works, our philosophy, and our methods. Second, Monty talked about the work we have done thus far, what’s already been incorporated into our MySQL fork, and what lies ahead. Finally, we opened the floor to questions. Thankfully a break was scheduled for after our talk, as the question period ran well over the session time limit. O’Reilly staff were very understanding, and graciously allowed us to keep using our session room.
One thing that was made clear is that we have not been communicating enough about exactly the kind of work we are doing. This is a failure on my part. In my defense, I have been somewhat reticent about pestering our development team for status updates, as I’m really keen on getting a GA release of MariaDB out ASAIMS (“as soon as it makes sense”). Mark Callaghan, one of our favorite users, was especially curious about what features and bugfixes we have implemented. He was quite cheerful about it, and declined to slap me for not being more communicative (thanks Mark!).
Some of these questions were answered in Monty’s portion of our presentation, and our slides are available from O’Reilly’s OSCON site. Grab the PDF and find out what we’ve been doing, and how we have been doing it!
Next week is our company meeting in Majorca, and I will be spending time with the dev team compiling a definitive list of what you can expect to find in the MariaDB GA release that is tentatively scheduled for later this month. I’ll blog about that as soon as I have the information, and also ensure it is put on the Maria wiki. Remember, we won’t release code we ourselves wouldn’t use in production. Thus, if the release date slips a bit, understand it’s because we’re committed to providing busy DBAs with production servers the very, very best.
Thanks again to Jono, the Postgres team, Tim O’R and Alison Randal at O’Reilly, and everyone else that made our week so fun and productive! And finally, apologies for the tardiness of this post. I have had house guests ever since returning from OSCON.
August 5, 2009
A few weeks ago I wrote a post about an acquaintance that had been given some very strange legal advice from a Sun sales rep. It generated a lot of interest, from both people inside Sun and those outside. Here’s what I have learned since:
1). Many people think that keeping your sources’ identities private makes the resulting information lies or FUD. They should talk to Woodward and Bernstein.
2). Many people cannot interpret a question mark at the end of a sentence. I was not making an indictment with my previous post, I was asking a question.
3). Most Sun employees do not make mistakes 1 and 2.
The third point is what prompts this post. Thanks to some concerned people inside Sun, the person who received the bad information now has a clear line of communication to get it resolved. I hope they do so.
Also, Sun has asked that anyone that feels that they have been given bad advice by a Sun sales representative contact a sales manager to get the straight dope. You can find a list of worldwide contacts on Sun’s worldwide MySQL sales team page.
Sun employees have also assured me that the sales rep mentioned in my previous post was incorrect, and was giving advice contrary to Sun’s policy. It seems clear that some re-training or better training is in order. I hope Sun takes this opportunity to better educate their sales staff.
August 5, 2009
My name is Kurt, and I’m a SELECTaholic … wait … wrong place. Strike that.
Thanks very much to Dups and Bryan Alsdorf for getting this all sorted.
July 18, 2009
Walter Cronkite has died.
Many people feel a connection to this man, a testament to his straightforward, approachable, and sincere nature. But that sense of connection is somewhat deeper for me.
In 1968, when I was 2.5 years old, I contracted spinal meningitis. I was hospitalized for over a month, and the prognosis included the possibility of death. In an effort to keep my mind off the daily routine of injections and tests, my parents would read to me, sing, and ask me what small wishes they might fulfill. I asked them to tell Walter Cronkite that I wanted to go to the moon with him.
A letter was sent to CBS headquarters in Manhattan, and in response I received a letter from the man himself, typed and signed by his own hand. He told me he would like nothing better than to travel to the moon with me, but that that meant I had to focus my energies an getting well. And that he hoped I would get well and that we could realize my dream together. The letter included a signed photo.
I did get well, and that letter and photo are still in my possession, and to this day rank among my most treasured belongings.
And that’s the way it is.
Goodnight, Mr. Cronkite. This world is a far more empty place without you.
July 6, 2009
As The Clash reminded us, Know Your Rights!
A good friend whom I trust implicitly recently told me of a disturbing conversation that had taken place between a DBA acquaintance friend of his and a Sun sales engineer. Disturbing enough that it prompts me to remind everyone what your rights and obligations are when you use the community edition of MySQL that is licensed under the GPLv2.
Apparently, this friend of a friend needed some performance tuning done on a MySQL Community Edition installation that spans several servers, and serves up their proprietary, commercial web application. They contacted Sun in order to see about getting some work done on a contractual basis. In other words, they wanted to pay Sun for performance tuning.
They were then contacted by a Sun sales engineer who, upon hearing they have multiple servers running the Community Edition of MySQL serving up a proprietary web app, told them:
1). They were in violation of the license.
2). They would need to release their proprietary app under the GPL, since it uses MySQL client libraries.
3). They could avoid having to GPL their application by paying Sun licensing fees for every server.
Now, I’m not a lawyer. But, in my legally uneducated but GPL-savvy opinion, there is a simple term for this. It’s extortion. “Pay us, or we’ll make sure you have to GPL your proprietary work.” If someone admitted to the bar in any US state wants to correct my opinion that this is extortion, chime in. I may be confusing terms.
However, I am not confused about the rights and obligations granted and ensured by the GPL. Let me cast some light into the darkness created by this Sun salesman.
First, this company uses the Community Edition of MySQL. Therefore, they are bound by the terms of the GPL, and NO other license, be it from Sun or elsewhere. Full stop. Sun can have whatever convoluted license they please for MySQL Enterprise, but if you use the Community Edition you are bound solely by the GPL.
The GPL ensures that anyone that releases code that touches GPL code must also use the GPL. The key word here is “releases.” Let’s give two examples.
First, Linksys recently settled a lawsuit brought against them by the Software Freedom Law Center. They use Linux kernel code in some of their router firmware, and had not released the source code to that firmware. Why did they have to? Because the firmware shipped to end users. They released code to the public in binary form that touches the GPL Linux kernel. Thus, they need to GPL their firmware.
Second, it’s no secret that Google uses MySQL extensively. So why aren’t GMail, Google Reader, Google News, or other such services released to the public under the GPL? It’s simple. They aren’t released at all! These are proprietary applications that are not released in either binary or source form. If your code touches GPL code, but you don’t release your code in binary or source form, you do not have to use the GPL for your code, nor do you run afoul of the GPL itself.
So, let’s go over the three points the Sun sales engineer made above.
1). They were not in violation of the license of the Community Edition MySQL server software they were using. To imply differently is at best misinformed, and at worst FUD.
2). They don’t have to release their code at all! Now, if they do decide to release their code, because it touches the MySQL client libraries they will have to use the GPL. But if they keep it a closed-source, proprietary, commerical app, with no public releases, they are well within their rights. Their application, developed in-house and run as a service on top of the MySQL Community Edition, is not released to the public in any form. Therefore, they do not have to use the GPL with their application or service, nor do they have to acquire commercial licenses from Sun. End of story.
3). They wanted to pay Sun for performance tuning. Sun decided to go for a bigger paycheck. In the end, Sun probably will not get a dime. Smart. Really, really smart. Glad I don’t own stock.
If Sun contacts you or someone you know and begins talking about license violations, read this post again carefully. Know your rights. And if you’re not sure, contact the Software Freedom Law Center. Or contact us at Monty Program; our staff was responsible for putting MySQL under the GPL. We know the terrain better than Sun.
If you have had a similar experience, I’d sure like to know about it. I’m curious as to how widespread this “tactic” is, and how people are responding to it and dealing with it. Let me know via comments.
And while we’re at it, if you need MySQL or MariaDB performance tuning, why contact a company that instead of seeing an opportunity to make a client happy while earning money instead sees an opportunity to extort money from a heretofore satisfied user? Contact the Open Database Alliance. We have people that can get the job done, and that don’t care about your licensing.
June 21, 2009
Comments Off on Midsummer!
Glad midsommar! Hauskaa juhannusta!
Best Midsummer wishes to all my Scandinavian friends and family!
Kristine and I are having a wonderful time visiting the crazy Swedish-Finn contingent of Monty Program. The food, songs, camaraderie, and 24 hours of daylight. Being with a close-knit group feels like they are a family, and their most excellent hospitality made us feel immediate part of that family. Our deepest thanks to Monty, Anna, Ralf, and Nina; our hosts and hostesses.
Here’s a nice photo of the Baltic near Nauvo (Nagu). Lots of water, but the sea, so no små grodorna.
May 27, 2009
The OpenBSD hackers are writing their own SMTPD. Anyone that says “what an absolute waste of time” has:
1). Never run Sendmail.
2). Doesn’t care if their SMTPD is not GPL-compatible (Postfix ain’t).
3). Too much free time and not enough experience.
I’m psyched for this. I’d love to see an SMTPD that
1). Has configuration files that need not be treated as binaries.
2). Is resource-friendly.
3). Is sysadmin-friendly.
4). Is secure.
In my experience, the OpenBSD crowd is among the most likely subset of Free Software and open source hackers able and willing to deliver on this wishlist.
Make me happy, guys!
« Previous Entries Next Entries »