The truth about MySQL Community and EnterpriseSat, Jan 20, 2007 in Databases
Late in 2006 MySQL decided to move to a split distribution model, Community and Enterprise. A lot has (apparently) changed since then, yet nothing has really changed since then. These things remain true:
- MySQL is freely available in both source and binary form – free as in freedom, and free as in beer.
- The MySQL community continues to get every single bug fix for free.
- The only real change the MySQL community sees is less frequent official binary builds. If you want the bleeding-edge code for which there is no official binary build, you can build it yourself.
What is unclear about that?
Some time before they officially announced this decision, one of the MySQL folks kindly gave me a call about the upcoming change. I was quite honored to get such a call – it communicated respect and genuine care for the community and for me as an individual (I am not a paying Enterprise customer). And I have to say, rarely have I been approached about a change like this with such an open mind and humility. Normally I’m accustomed to companies making decisions and just announcing them. The employee who called me, who shall remain nameless, simply told me about the internal discussions and asked for my feedback.
It took several minutes on the phone for me to get a sense of what they were proposing. Finally I gave my opinions, which I’m trying now to recall:
- I never like when anyone puts the word “enterprise” in their product. It is marketing speak. But I don’t care, let them name it what they like.
- I thought the decision would partially be a false economy because even though they’d save on the overhead of building binaries, I thought forking the codebase would be more work.
- I thought the decision would confuse people.
- I thought there would be an inevitable public slaying on Slashdot.
- I thought people would gripe a bit about not getting Community builds, but quickly figure out the changes and settle back to work.
- Finally, I thought the MySQL user community would be very supportive and understanding, since they get a great product for free.
The person who called me agreed in many ways, and as it turns out I was right on some points. But on the last two points I was dead wrong. Judging by public comment, a lot of people (mostly people who make off-topic comments on other people’s blog posts) are just not taking the time to read, think, and understand what’s changed. There are still people spreading misinformation all over the place.
And I now slightly regret my decision not to comment on the changes. Though this is a technically focused blog, it’s also very important for me to promote Free-As-In-Freedom Software through its pages, and I let that chance pass. MySQL was kind enough to solicit my feedback in advance, and I didn’t return the favor by helping people understand exactly what was changing.
Having met many of the MySQL employees in person at MySQL Camp, including the lead developers and founders, I have developed a personal loyalty to them as well as the company and product. I hope this gets straightened out soon.
And I want to take a chance to ask the MySQL employees to stop apologizing for being unclear. You were clear. It is not your fault some idiots jumped to conclusions and spread misinformation. It is incumbent upon every individual to assure he or she is speaking truthfully, by going to the source and taking a few minutes to get the facts straight. A lot of people didn’t do that, and it is not your fault. You can’t take responsibility for people who can’t be bothered to think.
About The Author
Baron is the founder and CEO of VividCortex. He is the author of High Performance MySQL and many open-source tools for performance analysis, monitoring, and system administration. Baron contributes to various database communities such as Oracle, PostgreSQL, Redis and MongoDB.