MariaDB
MariaDB is a free and open-source relational database management system (RDBMS) forked from MySQL, designed as an enhanced drop-in replacement that maintains full binary compatibility with MySQL while introducing additional features for improved performance, scalability, and reliability.[1] Developed under the GNU General Public License version 2 (GPLv2), it supports standard SQL queries, transactions, and a pluggable architecture for storage engines, making it suitable for a wide range of applications from web services to enterprise data management.[1] The project originated in 2009 when Michael "Monty" Widenius, a co-founder of MySQL AB and one of MySQL's original developers, initiated the fork following the April 2009 announcement of Oracle Corporation's acquisition of Sun Microsystems (which had acquired MySQL AB in 2008), amid concerns over the future openness of MySQL under Oracle's proprietary control.[2] [3] [4] This move ensured the codebase remained fully open-source and community-driven, diverging from Oracle's MySQL while preserving core functionalities.[5] MariaDB has since evolved independently, with regular releases incorporating innovations like advanced optimizer improvements and support for modern data types.[1] Governed by the non-profit MariaDB Foundation established in 2012, development is collaborative, involving contributions from a global community of developers, companies, and users, with multiple stable branches maintained for long-term support (typically 3 years of active maintenance plus 2 years of security fixes).[1] Key features include a rich ecosystem of storage engines—such as the default InnoDB for transactional workloads, Aria for crash-safe read-heavy operations, MyISAM for non-transactional speed, and MEMORY for temporary in-memory tables—along with built-in support for JSON documents, full-text search, geospatial indexing (GIS), and temporal tables.[6] These capabilities enable optimization for diverse workloads, from high-concurrency web applications to analytics and embedded systems.[7] As of November 2025, MariaDB ranks 9th in popularity among relational DBMS according to the DB-Engines Ranking, with a score of 87.36 based on metrics like search engine mentions, technical discussions, and job postings, placing it behind leaders like Oracle, MySQL, and Microsoft SQL Server but ahead of many other open-source alternatives.[8] Widely adopted in production environments, it powers applications at organizations ranging from startups to Fortune 500 companies, benefiting from its robustness and ongoing enhancements in areas like security and AI integration.[9]MariaDB Server
Licensing
MariaDB Server is released under the GNU General Public License version 2 (GPLv2), a copyleft open-source license that grants users the freedoms to run, study, share, and modify the software while requiring that any distributed derivatives remain open source under the same terms.[1] This model ensures that contributions and modifications to the server are shared back with the community, promoting collaborative development and preventing the enclosure of the codebase in proprietary products.[10] The adoption of GPLv2 traces back to MariaDB's origins in 2009 as a community-driven fork of MySQL, initiated by its original developers to preserve a fully open-source alternative amid concerns over MySQL's dual-licensing approach following Oracle's acquisition.[11] By committing exclusively to GPLv2, MariaDB avoided the commercial licensing dependencies that characterized MySQL, reinforcing its dedication to free software principles from the outset.[1] Under GPLv2's copyleft requirements, if users modify MariaDB Server and distribute the resulting binaries—such as in embedded applications or customized deployments—they must also provide the corresponding source code under GPLv2, ensuring ongoing openness and accessibility for all users.[10] This mechanism protects the ecosystem by mandating reciprocity in modifications, though internal use or non-distributed changes within an organization face no such obligations. For enterprise scenarios, MariaDB offers dual-licensing options through the MariaDB Corporation, where commercial licenses permit proprietary extensions and integrations without invoking full copyleft restrictions, allowing businesses to combine the server with closed-source components while complying with legal needs.[12] These commercial licenses include clauses that explicitly authorize such extensions, provided the core server remains GPLv2-compliant, balancing open-source ethos with enterprise flexibility.[11]Version History
MariaDB was initially released as version 5.1 on October 29, 2009, serving as a community-developed fork of MySQL 5.1 to ensure continuity in open-source relational database development following concerns over Oracle's acquisition of MySQL AB.[1] The project quickly progressed through early versions, including MariaDB 5.2 (December 2009) and 5.3 (May 2010), which introduced initial enhancements like the Aria storage engine for crash-safe operations. MariaDB 5.5, released in December 2012, marked the first long-term support (LTS) branch, providing five years of maintenance until its end-of-life in February 2020.[13] In 2014, MariaDB adopted a new versioning scheme with the 10.0 series (October 2014), emphasizing improved performance and new storage engines such as ColumnStore for analytical workloads. Subsequent innovation releases included MariaDB 10.1 (November 2015), which added GIS improvements; 10.2 (May 2016), introducing native JSON support and window functions; and 10.3 (November 2017), enhancing system-versioned tables for temporal data handling. The 10.4 series (June 2019) built on temporal capabilities with full support for system-versioned tables, while 10.5 (June 2020) focused on query optimization refinements; both were short-term releases ending support in June 2024 and June 2025, respectively. MariaDB 10.6, released in July 2021 as an LTS version, introduced CTEs (Common Table Expressions) and roles for access management, with support extending until July 2026. More recent LTS branches include MariaDB 10.11 (February 2023 initial stable), supported until February 2028, featuring aggregated innovations like improved parallelism from prior short-term releases (10.7–10.10). MariaDB 11.4, achieving stable release in May 2024, incorporated enhanced security features like improved authentication plugins and encryption defaults, with maintenance until May 2029. Starting in 2025, MariaDB adopted a yearly LTS release model with 3 years of support.[14] MariaDB 11.8, released in June 2025 as the first under this model, integrates vector search for AI-driven applications and is supported until June 2028. MariaDB 11.5 (August 2024) was a rolling release, no longer maintained as of November 2025.[15] The rolling 12.0 series, previewed in March 2025 with GA in August 2025, previews advancements in AI integrations and columnar storage optimizations, with the first LTS in the 12.x line (12.3) anticipated in 2026. Older branches, such as 10.1 (end-of-life October 2020), have been deprecated to focus resources on maintained versions.[16][13][17]| Major Version | Initial Stable Release | Support End | Key Innovations |
|---|---|---|---|
| 5.1 | October 2009 | February 2015 | Fork from MySQL 5.1; Aria engine introduction |
| 5.5 | December 2012 | February 2020 | First LTS; performance partitioning |
| 10.0 | October 2014 | March 2019 | New versioning; ColumnStore engine |
| 10.2 | May 2016 | May 2021 | JSON support; window functions |
| 10.4 | June 2019 | June 2024 | Temporal tables |
| 10.6 | July 2021 | July 2026 | CTEs; roles (LTS) |
| 10.11 | February 2023 | February 2028 | Improved parallelism (LTS) |
| 11.4 | May 2024 | May 2029 | Enhanced security (LTS) |
| 11.8 | June 2025 | June 2028 | Vector search for AI (LTS) |
| 12.0 | August 2025 (GA) | Ongoing (rolling) | AI integrations; columnar storage |