Difference Between Mariadb and Mysql

Difference Between Mariadb and Mysql

Mariadb is drop-in replacement for MySQL. The goal for Maria-DB is to be a drop-in replacement for MySQL – with more features and better performance. Mariadb development is led by some of the original developers of MySQL, who refuse to continue to work with Oracle Cooperation after take over Mysql. Below are some major difference between mariadb and mysql:

1. More Storage Engines:

These include the Aria, XtraDB (an enhanced and extended version of the InnoDB storage engine), PBXT, FederatedX (a drop-in replacement for Federated), OQGraph, and SphinxSE storage engines

2. Enhanced INFORMATION_SCHEMA:

The INFORMATION_SCHEMA has also been enhanced. MariaDB has added more data in various tables. For example, the INFORMATION_SCHEMA.PLUGINS table now has PLUGIN_MATURITY and PLUGIN_AUTH_VERSION columns, so you can see the version numbers of your plugins and whether a version you have installed is of stable, beta, or other quality.

3. Improved slow query log:

The slow query log has also been improved. In MariaDB, you can set the verbosity, filter out queries you don’t want logged, and limit the logging rate (e.g., to log only a quarter or tenth of the queries). As with other new features, the default configuration has this extra functionality turned off to be compatible with the behavior of MySQL.

4. Parallel Replication:

MariaDB 10.0 can execute some queries, replicated from the master, in parallel (simultaneously) on the slave. MariaDB replication in general takes place in three parts:

  • Replication events are read from the master by the IO thread and queued in the relay log.
  • Replication events are fetched one at a time by the SQL thread from the relay log
  • Each event is applied on the slave to replicate all changes done on the master.

5. Better Performance:

MariaDB claims it has a much improved query optimizer and many other performance related improvements.

6. Galera active-active master clustering

Galera is a new kind of clustering engine which, unlike traditional MySQL master-slave replication, provides master-master replication and thus enables a new kind of scalability architecture for MySQL/MariaDB. Despite that Galera development already started in 2007, it has never been a part of the official Oracle MySQL version while both Percona and MariaDB flavors have shipped a Galera based cluster version for years.

Other changes in MariaDB are not so visible, but they help to improve performance, give MariaDB more flexibility, or both.