MariaDB 11.7: The Fork That Keeps Its Own Path

javi
Sala de servidores con luces azules representando bases de datos en producción

MariaDB 11.7 (Nov 2024) consolidates the fork’s independent direction from MySQL. New features: integrated vector search, improved JSON, performance optimisations. This article covers news and when MariaDB remains a sensible choice vs MySQL 8 / Postgres.

11.7 Features

-- Create vector column
CREATE TABLE docs (
  id INT PRIMARY KEY,
  content TEXT,
  embedding VECTOR(384)
);

-- Insert with embedding
INSERT INTO docs VALUES (1, 'Hello', VEC_FromText('[0.1, 0.2, ...]'));

-- Similarity search
SELECT id, content FROM docs
ORDER BY VEC_DISTANCE(embedding, VEC_FromText('[...]'))
LIMIT 10;

Native — no extension needed. HNSW index support.

JSON Improvements

  • JSON_OBJECT_AGG: aggregate to JSON.
  • JSON paths: more expressive.
  • Performance: faster JSON operations.

Competitive with Postgres JSONB.

Other

  • Optimiser improvements: better query plans.
  • Replication enhancements: safer semi-sync.
  • Performance: benchmarks show 5-15% improvements vs 11.5.

MariaDB vs MySQL

Forked since 2009 (Oracle acquisition). Growing divergence:

Aspect MariaDB MySQL 8
License GPL GPL + commercial
Vendor MariaDB Foundation Oracle
Storage engines Aria, InnoDB, MyRocks, ColumnStore InnoDB primarily
Replication Galera multi-master Group replication
JSON Good Similar
Vector search Native Via MySQL HeatWave only
Community OSS-focused Oracle-influenced

MariaDB more “community-first”. MySQL more “Oracle-backed”.

MariaDB vs PostgreSQL

Different philosophies:

  • MariaDB: MySQL-compatible, storage engines, Galera multi-master.
  • PostgreSQL: rich feature set, extensibility, ACID focus.

PostgreSQL generally more capable. MariaDB better fit for MySQL-origin apps.

Storage Engines

MariaDB’s strength:

  • InnoDB: default, transactional.
  • MyRocks: LSM-tree, high-write workloads.
  • ColumnStore: OLAP columnar.
  • Aria: crash-safe MyISAM replacement.

Mix per use case. MySQL 8 mostly InnoDB.

Galera Clustering

Multi-master synchronous:

  • Galera: ships with MariaDB.
  • Automatic failover: any node accepts writes.
  • Streaming replication: new data distributed.
  • Split-brain prevention: quorum-based.

MySQL has Group Replication but Galera more mature and reliable for multi-master.

Upgrade

From 11.5 / 11.6:

apt upgrade mariadb-server
mysql_upgrade  # schema compat check

Compatible. Typically seamless.

From MySQL:

mysqldump → import to MariaDB
# or InnoDB file migration in some cases

Most MySQL apps work on MariaDB without changes.

When to Choose MariaDB

  • Legacy MySQL apps: drop-in replacement.
  • Galera multi-master needed.
  • Storage engine diversity relevant.
  • OSS philosophy preferred.
  • Community-driven priority.

When MySQL / Postgres Better

  • MySQL: Oracle ecosystem, HeatWave analytics.
  • Postgres: rich JSON/extensibility, strongest SQL standards.

MariaDB becomes a niche primarily: MySQL-like with multi-master + specific storage engines.

Enterprise vs Community

  • MariaDB Community (free).
  • MariaDB Enterprise (paid):
    • Long-term support.
    • Professional support.
    • Advanced security.
    • Additional tooling.

Similar model to Red Hat / CentOS arrangement.

Cloud Support

  • AWS RDS MariaDB: available.
  • GCP Cloud SQL: supports.
  • Azure: Flexible Server.
  • Self-hosted: Docker, Kubernetes.

Broad support.

Ecosystem

  • ORM support: MariaDB MySQL-drivers compatible everywhere.
  • Monitoring: Prometheus exporters work.
  • Backup: MariaBackup, mydumper.
  • Migration tools: maintained.

Mature ecosystem.

Performance Benchmarks

Orientation:

  • Read-heavy: comparable to MySQL.
  • Write-heavy MyRocks: advantage over InnoDB.
  • Galera cluster: reduced write performance vs single node.
  • JSON: improved but Postgres JSONB still wins.

Security

  • TLS: standard.
  • Row-level security: basic.
  • Audit plugin: enterprise available.
  • GDPR tools: enterprise.

Comparable to MySQL security profile.

Conclusion

MariaDB 11.7 consolidates independence path. Native vector search is relevant feature in 2024 LLM era. Galera multi-master remains strong differentiator. For MySQL-compatible needs with multi-master or storage engine variety, MariaDB recommended. For greenfield without legacy constraints, Postgres usually better choice. For Oracle-MySQL ecosystem shops, staying MySQL 8 probably easier. The fork matures independently — viable long-term.

Follow us on jacar.es for more on MariaDB, databases, and replication.

Entradas relacionadas