MariaDB for Adobe Commerce

Adobe Commerce is carrying MariaDB forward as its default and recommended database platform.

Adobe Commerce 2.4.8 and 2.4.9 are the final releases that support MySQL. MySQL 8.4 is the final MySQL version Adobe says it will certify or support for Adobe Commerce. Future Adobe Commerce releases continue on MariaDB.

For merchants, agencies, hosting providers and extension developers, that creates a practical question:

When should you move from MySQL to MariaDB, and how should you prepare?

MariaDB Foundation is working with the Adobe Commerce and wider Magento ecosystem to make that transition predictable, well documented and useful to the businesses making it.

Running Adobe Commerce on MySQL today?

Last checked: 25 August 2026

Start by identifying the MariaDB version supported for your Adobe Commerce release. Then assess, test and benchmark your own environment before moving production.

Adobe Commerce release	Commerce on Cloud	On-premises
2.4.9	MariaDB 12.3 recommended, 11.8 supported	MariaDB 12.3
2.4.8-p5	MariaDB 11.4 / 11.8	MariaDB 11.4 / 11.8
2.4.7-p10	MariaDB 10.11 / 11.8	MariaDB 10.11 / 11.8
2.4.6-p15	MariaDB 10.11	MariaDB 10.11
2.4.5-p17	MariaDB 10.11	MariaDB 10.11
2.4.4-p18	MariaDB 10.6	MariaDB 10.6

What Adobe has changed

MariaDB has been part of the Magento and Adobe Commerce ecosystem for many years. The important change is where Adobe is taking the platform next.

Adobe currently states that:

Adobe Commerce 2.4.8 and 2.4.9 are the final releases supporting MySQL.
MySQL 8.4 is the final MySQL release Adobe will certify or support for Adobe Commerce.
MariaDB is the default and recommended database platform going forward.
Adobe strongly recommends that Adobe Commerce 2.4.8 and 2.4.9 on-premises customers begin planning migration to MariaDB.
Customers on earlier supported Adobe Commerce releases are also being directed toward compatible MariaDB versions as the MySQL 8.0 support path ends.

MySQL 8.0 reached end of support on 30 April 2026. Adobe no longer validates newer MySQL major versions for the older Commerce release lines that depended on MySQL 8.o.

Read Adobe’s MySQL end-of-support and MariaDB guidance

MariaDB migration resources

MySQL → MariaDB Compatibility Matrix

A detailed reference covering important differences between modern MySQL and MariaDB releases.

Open the Compatibility Matrix

MySQL → MariaDB Migration Master Guide

Technical guidance covering preparation, migration methods, validation and common migration issues.

Read the Migration Master Guide

MariaDB Migration Tool

MariaDB Migrator provides a read-only Assess & Plan phase that can inspect a MySQL environment before data is moved, followed by several migration workflows including streaming, staged and replication-based approaches.

The tool is currently beta. Check its current supported source and target versions before selecting it for your Adobe Commerce migration.

Explore MariaDB Migration Tool

Adobe Commerce system requirements

Adobe’s authoritative list of database versions tested with each Adobe Commerce release.

Check Adobe system requirements

Adobe’s database transition guidance

Adobe’s explanation of MySQL end of support and its direction toward MariaDB.

Read Adobe’s guidance

Why MariaDB?

A familiar path from MySQL

MariaDB preserves much of the database model, protocol, SQL and operational knowledge already familiar to teams running MySQL applications.

That familiarity makes it possible to approach many migrations incrementally, while still assessing the areas where modern MySQL and MariaDB have diverged.

For an application ecosystem built around MySQL, that continuity matters.

An actively developed open-source database

MariaDB Server is developed as an open-source relational database through public development, releases and community participation.

MariaDB Foundation safeguards the continuity and openness of the MariaDB Server project and works with the wider technical ecosystem around it.

For organizations making a long-lived database decision, the open-source roots of the platform remain part of the path forward.

A modern feature path

The MariaDB you move to today is also a platform for capabilities that did not exist when many Magento installations were originally deployed.

Modern MariaDB development includes continuing work across query optimisation, replication, high availability, observability, extensibility and application development.

One example is native vector search.

MariaDB 11.8 LTS and later include a native VECTOR data type and VECTOR INDEX, allowing vector similarity search and relational SQL to operate together inside MariaDB.

That creates possibilities for commerce applications including:

semantic product discovery;
recommendations;
similarity search;
retrieval-augmented generation;
AI-assisted applications.

MariaDB stores and searches vectors. Applications still provide the embedding model and the user-facing integration.

Explore MariaDB Vector

MariaDB + Magento: what should we build next?

Adobe’s database direction makes MariaDB increasingly important to the commerce stack.

That also makes the ecosystem around MariaDB more important.

MariaDB Foundation wants to work with the Magento community on the pieces that make the database useful in practice, including:

predictable MySQL → MariaDB migration paths;
compatibility testing;
performance benchmarks;
hosting and deployment blueprints;
monitoring and operational tooling;
backup and recovery integrations;
extension compatibility;
real-world migration case studies;
reference deployments;
developer tooling;
semantic search and recommendation experiments;
MariaDB Vector integrations;
other capabilities the Magento ecosystem tells us it needs.

Some of these can become documentation.

Some can become code.

Some can become integrations, products, services, reference architectures or contributions maintained by companies already working in the Magento ecosystem.

If you build for Magento, we want to hear from you.

Who should talk to us?

Hosting providers

If you operate Magento or Adobe Commerce environments at scale, we want to understand what a repeatable MariaDB deployment and migration path needs to look like from the hosting side.

Agencies and integrators

If you manage Commerce upgrades, migrations or large merchant estates, help us identify the compatibility and operational issues that need better guidance.

Merchants

If you have a representative production workload, an upcoming migration or a database problem that can teach the wider ecosystem something useful, bring us the case.

Extension and tooling developers

If your product interacts with the database, we want MariaDB compatibility to be easy to test, document and communicate.

Performance specialists

If you work on Magento application and database performance, we want to build benchmarks around real application behaviour.

Search and AI builders

MariaDB already provides native vector search. The commerce-specific applications and integrations are still fertile ground.

What could we do together?

The best starting point is a real use case. From there, we can work together in different ways:

Migration collaboration — test a real MySQL → MariaDB migration, solve issues that come up, and turn the experience into a repeatable approach for other Adobe Commerce users.
Performance work — investigate real Magento workloads, benchmark them on MariaDB, and identify improvements in configuration, queries, tooling or MariaDB itself.
Hosting and solution stacks — develop and document a MariaDB-based Adobe Commerce setup that hosting providers, agencies or merchants can reuse.
Extensions and integrations — test or build products that work with MariaDB and make them easier for the Adobe Commerce ecosystem to discover and adopt.
Technical guides and case studies — document migrations, production architectures, performance work and other practical experience that can help the wider community.
MariaDB Ecosystem Hub — list relevant hosting, tooling, migration, consulting or extension offerings so MariaDB users can find companies already supporting the ecosystem.
Joint ecosystem activity — work together on content, events, benchmarks, demonstrations or other initiatives around a shared Adobe Commerce use case.
Upstream improvements — where a real Commerce workload exposes a gap in MariaDB or its tooling, work with us to improve it for everyone.
Partnership and sponsorship — build a broader relationship with MariaDB Foundation around technical collaboration, ecosystem visibility, joint programmes and support for the work needed to grow MariaDB adoption.