04.24.2008

The Future of MySQL

Back in January, Sun Microsystems acquired MySQL for about $1 billion.  This move made sense from Sun’s point-of-view as it provided a solid database product that could be re-marketed toward large enterprise environments.  Given Sun’s shift from hardware and proprietary software to a desire to implement open source solutions, the MySQL acquisition was another step in furthering that objective.

I’m left to wonder how strong Sun’s commitment to open source software really is after reading TechDirt’s take on What Sun Should Be Doing With MySQL.  Of particular concern to me is Sun’s moving specific new features to closed source development in an effort to push customers into paid support and versions.

Sun’s MySQL actions have some potential consequences.  First, Sun risks alienating loyal MySQL users and forcing them to look at other products.  One might argue that losing a customer that never paid for the software in the first place isn’t so bad, but many of the people that use MySQL in an unpaid installation also influence larger database decisions either through being loud and vocal or as part of career responsibilities.  The exodus from MySQL might also affect other companies that produce software that rely on MySQL such as CMS and personal publishing software companies.  And forcing those companies that currently rely on MySQL to seek alternative database solutions might be problematic in terms of software stability, new bugs, and overall product pricing.

While these problems may never manifest themselves, techno-slobs like myself may be in for higher hosting fees (due to software licensing) or new basic database instabilities.

Comments

Add a comment