Archive for the ‘Articles’ Category

Oracle-Sun Merger: Will MySQL survive?

Tuesday, June 23rd, 2009

The acquisition of MySQL AB, the people behind MySQL, the world’s most popular open source database, by Sun Microsystems earlier this year was not taken to very kindly by the open source community, in spite of the recent support that Sun has shown to open source technologies. Oracle’s (almost complete) buy-out of Sun Microsystems now has everyone wondering about the future of MySQL, especially with Oracle’s poor reputation in the open source space.

MySQL is estimated to have a more than 3 million installations worldwide, including those licensed under GPL. MySQL is present behind the scenes of thousands of very popular websites/companies today, including Facebook, Google and YouTube. Oracle is the world’s most widely used enterprise database system, and is being increasingly threatened by the popularity of MySQL. In this scenario, what does the buyout of Sun, and hence MySQL, imply for the millions of users of MySQL worldwide?

First of all, the current version of MySQL is distributed under GPL, which means that Oracle cannot kill it outright. It may stop support and development on it, but would this really matter? A majority of the existing patches have been developed by the community of users, as also most of the innovation. Online forums and interfaces are generally able to provide the support required by most users.

Oracle may stop development and support, but the development could still be forked to continue development. Of course, in this case, the product would have to be renamed due to trademark issues, but for a credible product like MySQL, a change in name would probably not matter much. A community developed branch, MariaDB, which has all the features of MySQL and was put together by some of the original creators of MySQL, is one such example.

It is possible that Oracle may sell MySQL to a third party because of anti-trust laws. Oracle does, after all, own the world’s best selling database platform, and owning two best-sellers in the top 5 could be a calling card for lawsuits against monopolistic competition. In this case, how things pan out will depend on who ultimately ends up owning it.

However, what will most probably happen is that Oracle will keep MySQL, provide support and development, and provide features that will make it easy for a user to quickly upgrade to the Oracle database platform. It will also possibly monetize the popularity of MySQL by developing proprietary support tools that offer value-add at a price. In addition, with a giant like Oracle at the helm, MySQL in particular, and open source in general, will surely find greater acceptance among all those large corporations that currently shy away from open source.

There is a very small chance that the shareholders of Sun, due to meet on July 16 for a vote, will strike down the merger despite the Sun board of directors having okayed it. If this is the case, MySQL will stay with Sun and users will definitely not have to worry much. Sun has been publicly supporting open source for some time now, and after the MySQL acquisition, has been trying (not very successfully, so far) to get the product to cater to both enterprise users and less sophisticated users. The only way forward that we see is for Sun to provide better support and development resources and, maybe, more value-add proprietary products. And, just like if Oracle were to own MySQL, there will be wider industry acceptance of open source architecture.

What this means is that over the course of the next few years, users of MySQL will not have to worry too much about having to change their database platform. What Oracle does with MySQL once the merger with Sun goes through is yet to be seen, of course, but like all the MySQL users around the world, we hope for the best.

Sources: www.sun.com; monty-says.blogspot.com; http://boycottnovell.com/2009/04/27/acquire-to-destroy-mysql/; http://www.softwarefreedom.org/blog/2009/apr/24/fork-well/

Drupal vs. Joomla – Which to Choose?

Tuesday, June 23rd, 2009

Web content management systems make creating and managing your website easy and mostly hassle-free. There are many web CMS systems out there, but mention open source web CMS to anyone and chances are that the response will include either Drupal or Joomla! (or both).

We’ll take a look at these two systems in this article, with the objective of helping you make an informed choice.

First, let’s look at what’s common between the two – and there’s quite a lot. Both are quite easy to setup. The learning curves for both are comparable, although, once again, for a non-technical person, Joomla! is a lot easier to figure out and has a more intuitive interface. Both work perfectly fine in a shared hosting environment. Both have plenty of multimedia and photo-gallery integration options. And most importantly, they have extensive community support, with any number of tutorials and (sometimes inconsistent) documentation, add-on modules and others.

Joomla! is great at complicated page layouts. Unfortunately, the html it generates is not so great, and tends to be quite difficult to manage. Also, it is not overtly search engine friendly (in spite of the improvements in version 1.5), which means that you’ll have to resort to other, external means if you need to optimize your site for search engines. Drupal, on the other hand, appears to put programming simplicity above complicated layouts and is very flexible. It generates simple code, and offers very search engine friendly features. Drupal also does a better job over Joomla! when it comes to managing multi-layer dynamic content. In addition, Drupal installations are multi-site, while a new Joomla! installation is required for every new site built using it.

If technology is a constraint, Joomla! supports only MySQL and Apache while Drupal supports, in addition, to these, IIS and PostGres. Drupal is also XHTML compliant.

Joomla! has more, and better, e-commerce related add-ons, compared to Drupal. So, if you’re looking to build a shopping website, using Joomla! will give you more shopping cart modules to choose from, and a variety of payment gateways that you can integrate into your website.

Joomla! has many easy to use templates that make life simpler. Drupal does not have many; in addition, creating templates on Drupal is not very easy.

Joomla!, as mentioned earlier in this article, is not very difficult to use, and someone with not much technical knowledge can have it up and running quite quickly. Drupal needs quite a bit of technical expertise to successfully exploit of all the functionalities it offers, and a non-programmer may find it difficult to understand the jargon that Drupal uses.

Large, rich sites can be created with both these systems. Each provides advantages over the other in different aspects. Finally, it all boils down to what kind of resources you have on hand and what it is that you’re developing. If you have bunch of experienced programmers, and are building, say, a social networking site with a large number of complex features, Drupal is the way to go. If you don’t have much programming resources on hand, and want to build, say, a complex e-commerce site, Joomla! is probably is your best bet.

Sources: http://buytaert.net/drupal-vs-joomla-performance; http://php.opensourcecms.com/general/ratings.php;
http://www.alledia.com/blog/general-cms-issues/joomla-and-drupal-which-one-is-right-for-you/;
http://www.communicopia.com/blog/joomla-versus-drupal