MariaDB vs. MySQL

MySQL is dead. Long live MySQL. Now that oracle owns MySQL, it will certainly kill it as quickly and quietly as possible. If you were a large corporation, why would you want to have a stable, open source, widely used software platform competing with your fee related software that is generating a profit from the corporate world. The short and sweet answer is you wouldn’t. That is why MySQL is going away.


Luckily the founder of MySQL, Michael Widenius left Sun and started his own community branch of MySQL, called MariaDB. MariaDB is a backward compatible, drop-in replacement branch of MySQL® Database Server which includes all major open source storage engines, including the Maria storage engine. You can find the MariaDB code at Launchpad, and download binaries at Downloads.

MariaDB is community developed, in collaboration with Monty Program

Start checking it out now peeps, it is coming and you better learn about it now.


About MariaDB

MariaDB 5.1 is based on MySQL 5.1 and is available under the terms of the GPL v2 license.

MariaDB will be kept up to date with the latest MySQL release from the same branch.

In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.

Currently the main differences between MariaDB 5.1 and MySQL 5.1 are:

In MariaDB 5.2, the new features are:

  • Group commit for the Maria storage engine. (faster)
  • userstatv2′, which creates several new information_schema tables with useful statistics information. You enable the statistics by setting the ‘userstat’ variable.

(for a definite and up-to-date list of features in 5.2, see MariaDB 5.2 page). has recently released MariaDB 5.1.41 RC for download and testing. You can download it here. It should be a drop in replacement for any recent MySQL 5.1 release.

As a final note, Oracle has made 10 promises regarding it’s commitment to Sun’s product line and is outlined here. Of course it should be noted that those promises were followed by a disclaimer called the “Cautionary Statement Regarding Forward-Looking Statement”
which makes quite clear that the document is in no way legally binding.

He that hath an ear, let him hear…


I am a g33k, Linux blogger, developer, student and Tech Writer for My passion for all things tech drives my hunt for all the coolz. I often need a vacation after I get back from vacation....

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.