Comments on: What Does Sun’s MySQL Acquisition Mean For Government IT Usage?

By: Jason Hull

Jason Hull — Thu, 14 Feb 2008 22:53:24 +0000

There are a lot of reasons for cost/time overruns. One of them would definitely be be using the wrong tool (or set of tools) for a given problem. In no way should anyone interpret this article to mean that I believe that Oracle is never the right answer for solving a given business problem. However, I do believe in considering as many of the right tools as possible, and opening up the suite to be considered to open source solutions (not just for databases, mind you) should yield better return on the money spent.

By: Maurice

Maurice — Thu, 14 Feb 2008 13:07:24 +0000

yeh right

up to a point using mysql is ok for some web 2.0 where a mega screw up has no political come back.

And developing on one db and delivering in anotehr just causes integration problems and at that late stage any problems get VERY VERY expensive to fix. You sould develop on indentical kit test on identical kit and deploy on identical kit!

And you not going to be able to use any of the neat stuff that oracle does if you develop using a LCD like mysql

If you are going to use a low cost db to develop and deploy on oracle atleast use Postgress as Postgress efectivly uses PL/SQL

““develop on the cheap, deploy on the big iron” no wonder Govenment it projects are notorious for over running on time and cost

By: Jason Hull

Jason Hull — Wed, 30 Jan 2008 02:08:56 +0000

There are a lot of forces against the introduction of a platform like MySQL from a grassroots genesis. Definitely the perceived safety and security of utilizing “big iron” is a big hindrance, because no PM or contracting officer wants to be the one that answers questions about why a name brand wasn’t used, regardless of whether it works, or, as importantly, regardless that many open source platforms (MySQL, Apache, etc.) are name brands. Another hindrance is that for platforms to be used in cleared facilities, they have to be approved. The process is definitely paperwork-intensive, and it is unlikely that many, if any, people have gone through the process to shepherd MySQL through that process. Given dedicated sales force and engineer support, MySQL can use Sun’s government expertise to walk a champion through the process, which will help adoption. After all, the wonks will say, if it’s good enough for use in cleared facilities, then it must be good enough for everyone else to use. I in no way mean to infer that the climb is short and gently sloped for MySQL’s adoption in the government.

Thanks for the comment, Duane!

By: Duane Gran

Duane Gran — Wed, 30 Jan 2008 01:51:22 +0000

I had the experience of installing mysql at two government agencies during my years in DC. The furthest I was able to go was to get mysql for testing, but in both cases Oracle was the required platform for production. This was progress because we didn’t need to purchase additional licenses for Oracle and it was an advantage to developers to use a lighter database platform. In one case our embrace of mysql nearly led to the opening of the code.

I suspect mysql has far greater penetration than the RFP pool would suggest. It sounds like the “develop on the cheap, deploy on the big iron” is still the mode in government circles.

By: Of interest: Sun, MySQL, and the US government at Xaprb

Of interest: Sun, MySQL, and the US government at Xaprb — Tue, 29 Jan 2008 17:42:41 +0000

[…] Jason Hull of OpenSource Connections, a company in my town, posted an article on what Sun’s acquisition of MySQL means for the US government. I thought Planet MySQL readers might appreciate a different angle on the issue than many of the Planet MySQL posts, which are often focused on business or community more than government. (I’m just passing the link along, not agreeing or disagreeing).Technorati Tags:government, Jason Hull, mysql, Sun […]