The MariaDB story is deeply personal. Michael 'Monty' Widenius didn't just create MySQL — he named it after his eldest daughter, My. When he created the fork, he named it after his youngest daughter, Maria. This is a man who names databases after his children, and he watched helplessly as his firstborn was sold to a company he fundamentally didn't trust.

The chain of events started in 2008 when Sun Microsystems bought MySQL AB for $1 billion. Monty, who had already left MySQL AB, wasn't thrilled but tolerated Sun. Then in 2009, Oracle — the world's largest proprietary database company — moved to acquire Sun. Monty went full alarm mode. He launched a 'Save MySQL' campaign, gathered 50,000 signatures on a petition to the European Commission to block the deal, and publicly warned that Oracle would slowly strangle MySQL to protect its own database business. The EC approved the deal anyway in January 2010, with Oracle making vague promises about MySQL's continued development.

Monty didn't wait around to see if Oracle would keep those promises. He had already started MariaDB in 2009, working through his company Monty Program Ab. MariaDB was designed as a drop-in replacement for MySQL — same APIs, same protocols, same feel — but with a commitment to staying truly open source. The fork attracted key MySQL developers and quickly gained features that MySQL lacked.

The adoption was dramatic. One by one, the major Linux distributions switched their default database from MySQL to MariaDB: Fedora, openSUSE, Arch, Slackware, and most significantly, Red Hat Enterprise Linux. Wikipedia migrated to MariaDB in 2013. Google switched its internal MySQL instances to MariaDB. The MariaDB Foundation was established in 2012 to ensure the project remained community-governed.

MariaDB's corporate story has had its own turbulence — MariaDB Corporation (the commercial entity, separate from the Foundation) went public via SPAC in 2022 and nearly went bankrupt in 2024 — but the open source project itself remains healthy and widely deployed. Meanwhile, Oracle has maintained MySQL as a viable product, somewhat proving the pessimists wrong about total abandonment, though many of Monty's concerns about open-source commitment have proven prescient.

MariaDB fundamentally altered the database landscape. By positioning itself as a drop-in MySQL replacement with better features and genuine open source governance, it forced a reckoning across the industry. Major Linux distributions, Wikipedia, Google, and countless enterprises migrated, proving that even a database as entrenched as MySQL could be successfully forked.

The fork also established a template for 'protective forks' — forks created not because the original is technically inadequate, but because the community fears what a new corporate owner might do. This playbook was later followed by LibreOffice, and variations of it echoed in Valkey (Redis) and OpenTofu (Terraform). Monty proved that the original creator of a project carries enormous moral authority when calling for a fork.