MariaDB 11.7: el fork que mantiene su propio camino

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

MariaDB 11.7 (Nov 2024) consolidates el fork en dirección independiente de MySQL. Features nuevas: vector search integrado, JSON mejorado, performance optimizations. Este artículo cubre novedades y cuándo MariaDB sigue siendo elección sensata vs MySQL 8 / Postgres.

Features 11.7

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

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

-- Búsqueda similarity
SELECT id, content FROM docs
ORDER BY VEC_DISTANCE(embedding, VEC_FromText('[...]'))
LIMIT 10;

Nativo — no extensión needed. HNSW index support.

JSON improvements

  • JSON_OBJECT_AGG: aggregate to JSON.
  • JSON paths: más expressive.
  • Performance: JSON operations faster.

Competitive con Postgres JSONB.

Other

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

MariaDB vs MySQL

Forked desde 2009 (Oracle acquisition). Divergence growing:

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 más “community-first”. MySQL más “Oracle-backed”.

MariaDB vs PostgreSQL

Different philosophies:

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

PostgreSQL generally más capable. MariaDB mejor fit para MySQL-origen 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: shipped with MariaDB.
  • Automatic failover: any node accepts writes.
  • Streaming replication: new data distributed.
  • Split-brain prevention: quorum-based.

MySQL has Group Replication pero Galera más mature y reliable para multi-master.

Upgrade

Desde 11.5 / 11.6:

apt upgrade mariadb-server
mysql_upgrade  # schema compat check

Compatible. Seamless typically.

Desde MySQL:

mysqldump → import to MariaDB
# o InnoDB file migration en algunos cases

Mayoría MySQL apps funcionan en MariaDB sin 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 se convierte en niche principalmente: 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 a 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 compatible MySQL drivers everywhere.
  • Monitoring: Prometheus exporters work.
  • Backup: MariaBackup, mydumper.
  • Migration tools: maintained.

Ecosystem mature.

Performance benchmarks

Orientation:

  • Read-heavy: comparable MySQL.
  • Write-heavy MyRocks: advantage sobre InnoDB.
  • Galera cluster: write performance reduced vs single node.
  • JSON: improved but Postgres JSONB sigue ganando.

Security

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

Comparable MySQL security profile.

Conclusión

MariaDB 11.7 consolidates independence path. Vector search native es feature relevante en 2024 LLM era. Galera multi-master sigue siendo fuerte diferenciador. Para MySQL-compatible needs con multi-master or storage engine variety, MariaDB recomendable. Para greenfield sin legacy constraints, Postgres usually better choice. Para Oracle-MySQL ecosystem shops, permanecer MySQL 8 probably easier. La fork matures independently — viable long-term.

Síguenos en jacar.es para más sobre MariaDB, bases de datos y replicación.

Entradas relacionadas