May 16, 2008   Sign In |  About ebizQ |  Contact Us |  Join ebizQ Gold Club
Dennis Byron
Open Source Software Up the Stack
Dennis Byron’s blog on open source software: A longtime market research analyst follows what “the movement” means to business integration—in applications, infrastructure, as services, as architecture and as functionality.

« Mulesource, WSO2, other OSS providers play the SOA platform card | Main | Elemenope, a great OSS project name and a good way to use OSS integration servers for BPM, supply chain automation »

January 16, 2008
Where does the MySQL community end up in a “megaOSS company?”

Marten Mickos, CEO of the about to be acquired MySQL, ended the January 16, 2007 morning press conference concerning Sun’s (JAVA) acquisition of MySQL by saying his “1000s of partners should find (the acquisition) excellent news.” That’s debatable when it comes to partners such as HP (HP), IBM (IBM), and Unisys who compete with Sun. Or Google (GOOG), which doesn’t like being too tightly tied to any of the big IT providers, which is why Google is one of the biggest financial supporters of—if not contributors to—the open source software (OSS) movement.

But the acquisition will be helpful to the MySQL community including the OSS-heritage hybrids we tend to talk to and talk about here most often on the ebizQ.net Open Source blog and in the ebizQ Open Source Feature Articles section. These include Alfresco, JasperSoft, Pentaho, Red Hat, SugarCRM, Talend and others. I have been writing both here and on Research 2.0 (see link to right) frequently in our year-end review articles about the convergence of the OSS community with the large enterprise software providers. Although Sun is one of those large providers, the good news is that Sun is the most committed of those providers to the OSS concept.

Sun’s in fact a “megaOSS company,” to coin a term. It has projects ongoing at all levels of the stack: Glassfish, openSolaris, OpenESB, openOffice, and so forth. It will certainly continue to provide the MySQL community similar support. And it has conditioned its shareholders already for the different way that OSS pays off on the income statement, the dependence on subscription maintenance and the apparently unprofitable relinquishing of intellectual property assets.

One thing I am concerned about is what this acquisition means for Sun’s other efforts in the OSS database field. Sun has contributed to both the JavaDB (Berkeley) and postgreSQL efforts. It says it will continue that participation but human nature argues against it. To the extent those communities depended on Sun, it’s time to investigate other options.

Perhaps they could do a “Google search” for possible new corporate sponsorship.

Posted by dennisb in OSS Business Issue |Digg This|Add to del.icio.us

Trackback Pings

TrackBack URL for this entry:
http://www.ebizq.net/mt/mt-tb.cgi/3048

Comments Post a comment




Remember Me?

(you may use HTML tags for style)

We ask that you type your code (displayed below) in the text box.This code is an image that cannot be read by a machine. It prevents automated programs from submitting comments.


Code:



Most Recent ebizQ Blog Entries
ADVERTISEMENT
Subscribe to this blog’s feed
My Work Elsewhere
Blog Roll
This Work
Accountability:The opinions expressed in this blog are solely representative of the blog's author, and not of ebizQ

Subscribe to our Newsletters
ebizQ Weekly Gold Club Update
Live Webinar Updates
Updates from ebizQ Partners
ebizQ SOA Update
ebizQ BPM Update
ebizQ Security Update
ebizQ BI Update
ebizQ Open Source Software Update
Virtual Show Newsletter
ebizQ Web 2.0 and the Enterprise
Your E-mail Address:
PepsiAmericas: Realizing Real-Time Communication
a refreshing approach to ESB and data integration

Date: May 28, 2008
Time: 13:00 PM ET
(17:00 GMT)

REGISTER TODAY!
Accelerate Agility and Lower Costs by Virtualizing and Governing Your SOA
Date: May 29, 2008
Time: 12:00 PM ET
(16:00 GMT)

REGISTER TODAY!
Archived Webinars | Upcoming Webinars

Marketing Solutions | Feedback | About ebizQ | Unsubscribe | Privacy Policy | Site Map