MySQL vs MariaDB: Which MySQL Lineage?
MySQL is the original database now stewarded by Oracle; MariaDB is a community-driven fork created by MySQL founders, largely drop-in compatible.
MariaDB forked from MySQL and stayed close to it, with shared client protocols and SQL, but the projects have diverged over time. MariaDB adds storage engines (Aria, ColumnStore), some unique features, and a fully open governance. MySQL benefits from Oracle investment and broad enterprise support. For most apps they are interchangeable, but newer features and specific engines differ.
| MySQL | MariaDB | |
|---|---|---|
| Origin | Original (Oracle) | Community fork |
| Compatibility | Reference | Mostly drop-in |
| Storage engines | InnoDB focus | InnoDB + Aria/ColumnStore |
| Governance | Oracle-led | Open foundation |
| Best for | Oracle ecosystem, parity | Open governance, extra engines |
Compatibility and features
For standard CRUD and typical web apps, you can often swap one for the other. Divergence shows up in newer JSON functions, system-versioned tables, specific replication features, and storage engines. Check the exact features your app relies on before assuming full parity.
In CI
Both run as service containers with near-identical setup; pin the version explicitly since defaults differ. Either works on managed runners, where faster runners shorten startup and migration test steps.
The verdict
Want the reference implementation with Oracle backing and broadest compatibility expectations: MySQL. Want fully open governance plus extra storage engines and features: MariaDB. They remain close enough that many teams choose based on hosting, licensing comfort, or specific feature needs rather than raw performance.