Back to all use cases

ConsultingCross-Industry

Test the compatibility questions on a copy before anyone commits to a move

Platform Engineering Team

A typical consulting engagement for a team considering a move from MySQL to MariaDB: a compatibility test of SQL, replication format and client libraries, and a parallel-running plan with a rollback.

MariaDB consulting

Overview

A typical engagement starts with a team that runs MySQL and is weighing a move to MariaDB, or the reverse after an acquisition. Both are described as compatible, and the team wants to know what actually differs for its own schema, queries and replication.

Challenge

MariaDB and MySQL started from the same code and have diverged. Global transaction identifiers use different formats, so replication across the two cannot be assumed to work; the system tables and some data types differ, including the JSON type, and the optimizers choose plans differently. Client libraries and authentication plugins may also behave differently. None of this is visible from the version numbers; it shows up in a test with the team's own workload.

Environment

A MySQL primary with replicas, applications in several languages through different client libraries, a schema with JSON columns and stored routines, and a nightly batch window.

Approach

AceMQ engineers restore a copy of the schema and a sample of data into MariaDB, run the application's test suite and a replay of captured queries, and compare results and EXPLAIN FORMAT=JSON output for the queries that matter. They test replication from the existing primary into a MariaDB replica and note what does not work, and they check client library versions and authentication. The plan sets parallel running by service and a rollback for each.

Solution

  1. Inventory of schema objects, data types, stored routines and client libraries
  2. Copy restored into MariaDB, with the test suite and a captured query replay run against it
  3. Query plans compared with EXPLAIN FORMAT=JSON for the queries that matter
  4. Replication between the two tested, with differences recorded rather than assumed
  5. Authentication and client library behavior checked
  6. Parallel running and cutover by service, with a rollback for each

Outcome

The engagement delivers a compatibility report, a list of changes needed in schema and code, a plan for parallel running and a rollback, and a recommendation that may be to stay where the customer is. The team's own developers make any code changes, and AceMQ engineers can run the first cutover with them.

Technologies

MariaDBMySQLLinux

Need MariaDB Architecture Guidance?

AceMQ's senior MariaDB engineers have handled this exact type of engagement before. Whether you need architectural guidance, hands-on remediation, or an ongoing managed partnership, we're ready to help.