Difference between revisions of "MariaDB"
| Line 2: | Line 2: | ||
MariaDB intends to maintain high compatibility with MySQL, ensuring a drop-in replacement capability with library binary parity and exact matching with MySQL [[Application programming interface|APIs]] and commands. It includes the [[XtraDB]] storage engine for replacing [[InnoDB]], as well as a new storage engine, [[Aria (storage engine)|Aria]], that intends to be both a transactional and non-transactional engine perhaps even included in future versions of MySQL. | MariaDB intends to maintain high compatibility with MySQL, ensuring a drop-in replacement capability with library binary parity and exact matching with MySQL [[Application programming interface|APIs]] and commands. It includes the [[XtraDB]] storage engine for replacing [[InnoDB]], as well as a new storage engine, [[Aria (storage engine)|Aria]], that intends to be both a transactional and non-transactional engine perhaps even included in future versions of MySQL. | ||
| + | |||
| + | ==See also== | ||
| + | https://dzone.com/storage/assets/10475078-mariadb-enterprise-comparison-wp.pdf | ||
Revision as of 16:15, 7 April 2019
MariaDB is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. Development is led by some of the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle Corporation.
MariaDB intends to maintain high compatibility with MySQL, ensuring a drop-in replacement capability with library binary parity and exact matching with MySQL APIs and commands. It includes the XtraDB storage engine for replacing InnoDB, as well as a new storage engine, Aria, that intends to be both a transactional and non-transactional engine perhaps even included in future versions of MySQL.
See also
https://dzone.com/storage/assets/10475078-mariadb-enterprise-comparison-wp.pdf
