This tip originally appeared on TechTarget's Expert Answer Center as a post in Craig Mullins' blog. Craig served as the on-demand expert on the Expert Answer Center for two weeks in February, during which he was available to quickly answer questions on EAC topic as well as to write daily blog entries. Keep an eye on the Expert Answer Center for topics that could help your IT shop.
Open source is a rolling freight train that cannot be stopped, as much as Microsoft may want to stop it. LAMP architectures will be used for certain database applications and systems that meet a specific set of criteria. LAMP stands for Linux, Apache Web server, MySQL database and the PHP/Python/Perl development languages. It is a collective of open source software that can be used to deploy applications with minimal cost, which is the intriguing part to most of its adopters.
The "no cost" aspect of open source and LAMP is both a positive and a negative. It is positive for the obvious reasons; I mean, no one wants to spend money for something if they can avoid it, right? Of course, the "no cost" label only applies to the initial acquisition cost of the software, and then only maybe. Red Hat, MySQL and others sell distributions of the software to make implementation and management easier. Additionally, support is crucial. Do you really want to implement a mission-critical application on free LAMP software and then not have anyone to turn to if problems occur? In other words, who will support the software when you have issues? Companies exist that sell this support. But now if we are buying the software and support to go along with it, how much different is it than commercial software?
At any rate, open source and LAMP will succeed for those projects that could not be cost-justified or are not affordable with commercial OS/DBMS/Web server software. As the projects gain acceptance in the company, additional support can be purchased to ensure the viability of the applications.
But would I predict that a major insurance company, for example, would implement its policy and customer system on "open source"/LAMP technologies? Nope. Never. That is not the "sweet spot" for open source. So, will open source databases ever become popular enough to strongly compete against Microsoft, Oracle and IBM for the database consumer's dollar? I don't think so. Open source DBMS software will be used in conjunction with the major enterprise DBMSs and in SMBs that cannot cost-justify an enterprise DBMS.
Interestingly, I think open source database technology will face some problems in the near-term future. The major open source DBMS products (MySQL, Firebird, PostgreSQL and Sleepycat) are mostly simpler to use than enterprise DBMS products because they do not have all the bells and whistles of the enterprise software. Over time, these are being added to the open source players. Triggers, stored procedures, integrity constraints and so on will make the open source DBMS products more complex to use, and, therefore, smaller organizations will have more difficulty deploying them rapidly. The software may be moving away from its sweet spot in terms of how and when it is implemented.
An interesting twist to the open source DBMS issue is the recent entry of Computer Associates to the game. In May 2004 CA announced that the release of its Ingres relational DBMS product into the open source community. Ingres was released under the CA Trusted Open Source License (CA-TOSL). Under the CA-TOSL, independent software vendors can incorporate Ingres into their products as long as the Ingres source code is provided with the product. CA will offer support and indemnification as added-cost options to the CA-TOSL Ingres. The Ingres source code is available here.
This move by CA gives open source developers another database option. This is good news for developers, but the open source DBMS market is already somewhat crowded with MySQL, PostgreSQL, Firebird and Sleepycat Berkeley DB. Furthermore, PostgreSQL grew out of the original Ingres DBMS, so now we have both Ingres and PostgreSQL available as open source software. Perhaps the growing acceptance of open source (and PostgreSQL) in the market place helped to force CA's hand in turning over Ingres to the open source community.
The bottom line is that there is a wealth of options if you are interested in using an open source DBMS product. But know what your needs are and what features are available in the open source DBMS products before diving headfirst into the open source waters.