Sun buys MySQL – now what?

Interesting news greets us this morning with Sun’s acquisition of MySQL.  (Congratulations are in order for both parties.)

I think a lot of us are still at the "oh wow" stage.  There are lots of implications.  It seems like a good fit because of Sun’s deep involvement in the Open Source community. 

The partnership will certainly juxtapose some interesting personalities: now we have Josh Berkus (PostgreSQL) and Monty (MySQL) working for the same company.

What will happen with licensing?  Will MySQL still be available under a
dual GPL/commercial license, or is it likely to end up under CDDL/SCSL or
similar?  Changing from one open source license to another can be an
extraordinarily difficult challenge both logistically and ecologically.

I note that I read in Don MacAskill’s blog that

"Maybe MySQL will finally start fixing all the performance/concurrency
issues with InnoDB (basically, InnoDB’s threading and concurrency
aren’t working well with modern multi-core CPUs). Google’s had some fabulous patches for awhile, and the brilliant Yasufumi Kinoshita does as well, but they don’t seem to be making their way into MySQL anytime soon." 

This is not going to happen as far as I know, because the patches were contributed under the GPL, and can’t be incorporated into the commercially licensed version.  In addition, Innobase Oy is owned by Oracle.  I think we’re more likely to see those performance and concurrency issues solved by using Falcon.

It’s also interesting from a Java perspective: traditionally Oracle has been the Database-of-Choice for Java devs, and MySQL for PHP devs.  With Sun producing MySQL we can expect to see better support within the Java community, although the press releases all note that support for the PHP/Rails/etc communities will continue.

It’s going to be another interesting year in Open Source.  I’m looking forward to it.