Friday, February 5, 2010

Oracle + Sun = ???

I know that this whole thing started long ago, and there's been a lot said (and written) about this topic, but I still haven't made up my mind about the overall impact. Particularly on Java - which is near and dear to my heart. Their main emphasis so far seems to be on the fact that they can now offer the full stack; from low-level hardware to software, including multiple enterprise applications spanning several verticals. But what is this going to mean to the peons that are still in the trenches, slinging code every day?

On the one hand - we now have a company with deep pockets and the ability to invest in Java as a platform. Oracle is saying that they plan to hire close to 2,000 people, many of which are expected to be technical (engineers, etc.). You might expect this to create significant growth in Java, along with better (and simpler) integration with all of the software/tools/frameworks already under the Oracle umbrella.

They are also pledging "certified" systems and unique support opportunities, where there is only "one place to call' to resolve issues. While this all sound great in the board room, how is this going to translate in the real world?

Well, I don't have the answer to that, other than to say that the only certainty is that things will change. Particularly in areas where there is clear overlap between the Sun and Oracle offerings, things like:
  • Development tools - I don't see JDeveloper and NetBeans co-existing (and Oracle has made no secrets about sticking with its "own" tools as the strategic direction for most products).
  • Application servers - While GlassFish is touted as the reference implementation with and "enterprise-ready" feel, it pretty clearly overlaps the current Weblogic offering.
  • Database servers - Clearly, no one expects MySQL to just go away, but its hard to know how that will play with product that drive Oracle's rise, their own flagship database.
There are other cultural differences that may play into things too - regarding open source directions, Java Community Process, and general approach to innovation Sun had more of a history of supporting projects that looked innovative, regardless of whether or not they would lead to real revenue. While this may have been a factor in their demise, I still am concerned about the prospects of losing choices in these areas.

I guess we'll just have to wait and see what the future brings, but if history is any indicator, I don't think the change will happen overnight. These things always take time...

No comments:

Post a Comment