// the find
MariaDB/server
MariaDB server is a community developed fork of MySQL server. Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry.
MariaDB is Oracle's MySQL fork that became its own thing — started by the original MySQL developers after Oracle acquired Sun, and it has diverged enough over 15 years that it's no longer a clean drop-in replacement despite what the README claims. It's a production-grade relational database used everywhere from small VPS setups to large clusters via Galera.
The storage engine plugin architecture is genuinely flexible — you can swap in RocksDB, Aria, or Spider without recompiling. Temporal tables (system-versioned) landed in MariaDB years before MySQL and are actually useful for audit trails without reaching for triggers. The vector search support (MHNSW index) was added natively, so you're not bolting on a separate service for simple nearest-neighbor queries. MariaDB Backup (fork of Percona XtraBackup) handles hot physical backups without locking, which is what you actually need in production.
The 'drop-in replacement for MySQL' framing is increasingly misleading — replication format differences, divergent JSON handling, and auth plugin gaps mean migrating from MySQL 8.x to MariaDB 10.x or vice versa requires real testing. The vector search implementation is new and unproven at scale compared to pgvector or dedicated solutions; the MHNSW index behavior under concurrent writes isn't well-documented. Galera cluster adds a lot of operational complexity and has hard limits around DDL operations and large transactions that will surprise anyone who treats it like regular replication. The codebase is C with C++ bolted on over decades — contributing or debugging internals requires navigating a lot of legacy accumulated from the MySQL 5.x era.