MariaDB Consulting & Support

MariaDB Consulting for Galera, MaxScale, Upgrades and Recovery

MariaDB consulting from AceMQ covers Galera and MaxScale design, upgrades from 10.x to 11.4, 11.8 or 12.3 LTS, backup and recovery testing, query and InnoDB tuning, and moves between MySQL and MariaDB, led by senior engineers who also staff the 24/7 MariaDB support rota. Engagements are quoted per engagement.

A senior engineer, not an SDR. No sales sequence attached.

Fastest response target, by plan
15 min
On-call cover
24/7
AceMQ customers
160+
Years in business
10+

Without treating MariaDB as MySQL with a new nameFor production incident cover, see AceMQ MariaDB 24/7 support.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

The Problem

Why teams call us about MariaDB

Eight MariaDB problems an AceMQ review starts from, from endless state transfers to a restore nobody has timed. If one describes your week, that is where the review starts.

  1. 01

    A Galera joiner repeats state transfers and never finishes

  2. 02

    The cluster dropped to non-Primary after a network partition

  3. 03

    Flow control throttles every writer because one node is slow

  4. 04

    MaxScale routes reads to a replica that is behind

  5. 05

    GTID errors after promoting a replica

  6. 06

    Queries that were fast on 10.x slowed after a move to 11.x

  7. 07

    Nobody has restored last night's backup to see how long it takes

  8. 08

    A move between MySQL and MariaDB is planned without a compatibility test

A good fit if MariaDB holds production data and you want one team that designs the cluster, times the restore and answers when quorum is lost.

Not a fit for small teams with non-critical workloads. AceMQ is not a budget consultancy: we work with enterprises running business-critical and compliance-heavy MariaDB.

Running MariaDB in production? Get a quote from a senior engineer, answered within one hour.

Contact Us

How it breaks, and the fix

What happens when a MariaDB primary fails and the promoted replica is behind?

With asynchronous replication, a replica applies changes after the primary commits them. If the primary fails while a replica is behind, promoting that replica discards the transactions it has not yet received. The GTID positions on each server show which replica is furthest ahead.

One failed primary, one lagging replica

Application, MaxScale, the primary and two replicas

Illustrative
  1. Both replicas keep up with the primary, and MaxScale routes writes to it and reads across the replicas.

  2. The primary fails while replica 1 is far behind. Writes are blocked, and promoting replica 1 would lose the transactions it has not received.

  3. The replica with the most advanced GTID position is promoted, MaxScale routes writes to it, and the lagging replica is rebuilt or repointed.

On MariaDB, gtid_slave_pos, gtid_binlog_pos and gtid_current_pos on each server show who is ahead, and log_slave_updates decides whether a replica can serve as a source for others. MaxScale limits stale reads with max_slave_replication_lag and causal_reads on the read-write split router. The design question is how much lag the application can tolerate, and whether semi-synchronous replication or Galera is the right answer for data that must not be lost.

Our Services

MariaDB Consulting & Services

AceMQ runs five MariaDB service lines: health check, Galera and MaxScale design, upgrade planning, backup and recovery testing, and MySQL and MariaDB moves. A senior engineer leads each one, and any of them can roll into 24/7 support.

  • 01

    MariaDB Health Check

    The fixed-scope entry engagement: a written report on how your MariaDB is configured and where it is exposed, which your team can act on with or without AceMQ.

    • Topology, node count and quorum design
    • gcache, flow control and applier settings
    • Slow queries, indexes and InnoDB sizing
    • Backups, binary logs and restore
  • 02

    Galera and MaxScale Design

    Quorum, state transfer and routing designed for the failures your estate can have.

    • Node count and arbitrator placement
    • SST method and gcache sizing for incremental transfer
    • MaxScale routing, lag limits and failover
    • Failure drills with a runbook
  • 03

    Upgrade Planning

    A written path from 10.x to 10.11, 11.4, 11.8 or 12.3 LTS, rehearsed on a replica with real traffic.

    • Version path and optimizer changes checked
    • Rolling upgrade node by node on Galera with mariadb-upgrade
    • Client authentication and TLS defaults
    • Rollback for each step
  • 04

    Backup and Recovery Testing

    A restore that has been timed, and a point-in-time recovery that has been replayed, rather than assumed.

    • mariadb-backup full and incremental runs checked
    • Binary log replay to a chosen time
    • Restore time measured against your objective
    • Runbook and schedule
  • 05

    MySQL and MariaDB Moves

    Moves in either direction after a compatibility test of SQL, replication format and client libraries.

    • SQL and replication compatibility tested
    • GTID and system table differences handled
    • Parallel running and cutover by service
    • A rollback for every step
  • Response targets from 15 minutes, by plan

    24/7 MariaDB Support

    Named senior engineers on your account — response targets from 15 minutes, by plan, no ticket routing.

    • Response targets from 15 minutes, by plan
    • Named engineer, zero cold-start
    • Proactive CVE & health monitoring
    • Quarterly deployment reviews

Want AceMQ to take this off your team's plate? Tell us about your MariaDB estate.

Contact Us

24/7 Support

MariaDB Support When It Matters Most

AceMQ MariaDB support gives you an AceMQ engineer and response targets from 15 minutes, by plan, when a cluster is down, 24/7, on Community and Enterprise Server.

  1. From 15 min (by plan)first responseEmergencyProduction down, messages not flowing, queue manager failure
  2. 1 hourfirst responseCriticalSevere degradation, high error rates, approaching capacity
  3. 4 hoursfirst responseHighPerformance issues, configuration problems, non-critical failures
  4. Next Dayfirst responseStandardQuestions, guidance, best practices, non-urgent improvements

Response targets by plan; your contract sets the tier.

P1 escalation path

A replay of one P1, from the first page to the written root-cause analysis

SLA 15:00
T+Elapsed15:00
Engineer on your bridge

Response targets from 15 minutes, by plan; 24/7.
A response time, not a resolution time.

  1. T+00:00

    P1 opened, on-call engineer paged

    Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.

    Paged
  2. T+15:00

    Senior engineer on your bridge

    A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.

    Live
  3. T+30:00

    Specialists across the stack join

    When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.

    If needed
  4. After

    Written root-cause analysis

    Root cause, the fix applied and the prevention steps, delivered after every P1.

    Every P1

How Our Support Actually Works

Beyond SLAs — the model behind senior-only, zero-cold-start expert access.

  • Named Engineers on Your Account

    Every ticket is handled by a senior SME assigned to your account — not a pool of anonymous agents. Zero cold-start. No re-explaining your environment.

  • Live Escalation on Any Ticket

    Any ticket can be escalated to a live session with your named engineer via calendar booking. No gatekeeping, no approval required — direct access, always.

  • Proactive Risk Mitigation

    Quarterly health checks on your deployment plus shared intelligence from our support customers — we surface risks before they reach production.

  • Critical Bug & CVE Intelligence

    Proactive alerts on critical bugs and CVEs affecting your exact version, with version compliance monitoring so you're never caught off guard.

  • Commercial EOL Versions

    Commercial support for end-of-life MariaDB versions, with security fixes backported through OSSeva, so the upgrade happens on your schedule rather than the community's.

How It Works

What actually happens next

An AceMQ MariaDB engagement runs in four stages: a scoping call with a quote within 1 hour, a review, a written plan, then the work or a handover. Each stage ends in writing.

Quote within 1 hour

Scoping call and quote

A senior AceMQ engineer asks what you run: the MariaDB release, Community or Enterprise Server, Galera, MaxScale or asynchronous replication, the hardware or cloud, the backup method, and what has prompted the question. A quote request is answered within 1 hour.

Scoped per estate

Review

Cluster topology and node count, gcache size against how long a node can be away, flow control and applier settings, GTID and replication state, the slow query log and ANALYZE FORMAT=JSON on your real workload, and a restore of a backup to a scratch server. Findings are written down and your team keeps them.

Scoped per estate

Written plan

A recommendation in writing: the topology and configuration changes, the upgrade path with a rehearsal on a replica, and the recovery procedure with a measured restore time.

Ongoing or fixed scope

Run the work or hand over

Changes staged one node at a time, each with a rollback. The work ends with runbooks for quorum loss, state transfer and restore. You can stop there, add 24/7 MariaDB support, or have AceMQ run the estate.

  • Written findings before any change
  • Changes staged and reversible, with a rollback plan
  • Your engineers in the room
  • Ad hoc engagements or an annual partnership

A senior engineer, not an SDR. No sales sequence attached.

Customer Success

Real MariaDB Results

Typical MariaDB engagements, described as scopes. Each card links to the full write-up.

1 / 6 case studies

  • Consulting

    MariaDB Backup and Point-in-Time Recovery Rehearsal

    Platform Engineering Team

    A typical consulting engagement for a team whose MariaDB backups run every night but have never been restored: a timed restore to a scratch server and a binary log replay to a chosen point in time.

    MariaDBLinux
  • Consulting

    MySQL to MariaDB Compatibility Test and Move Plan

    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.

    MariaDBMySQLLinux
  • Support

    MariaDB Galera Quorum Loss and Split-Brain Support

    European Telecommunications Operator

    Recovering a four-node Galera cluster after a site-link failure left both halves non-Primary, and redesigning it so one link fault cannot do that again.

    MariaDBGalera ClusterMaxScaleLinux
  • Consulting

    MariaDB 10.6 to 11.8 Upgrade Planning on Galera

    Healthcare Benefits Administrator

    Planning and rehearsing a rolling upgrade from MariaDB 10.6 to 11.8 on a Galera cluster, around the optimizer, TLS and change buffer differences.

    MariaDBGalera ClusterTerraformLinux
All use cases

Solutions

Every way AceMQ works with MariaDB.

AceMQ covers MariaDB end to end. Projects: consulting and implementation, health checks and migrations. Ongoing cover in four tiers, from 24/7 support and incident management to proactive monitoring, managed MariaDB on your infrastructure and fully managed MariaDB on AceMQ infrastructure, plus end-of-life versions.

Projects

Build, fix or move MariaDB

Fixed-scope work led by a senior engineer: architecture and new builds, a health check of what you run today, or a migration with a reversible cutover.

Side by side

MariaDB Enterprise support, AceMQ consulting or both: what changes?

MariaDB plc sells Enterprise Server subscriptions with Standard and Premium support, and Community Server is outside that support offer. AceMQ consults on and supports Community and Enterprise Server. Each row answers one question about the choice.

MariaDB subscription support and AceMQ consulting compared on who is covered, what the work is and how each is bought
QuestionMariaDB subscription supportAceMQ consulting and support
Who is covered?Enterprise Server and MaxScale subscribers; Community Server is not included in MariaDB's support offer.Community and Enterprise Server, Galera and MaxScale.
What is the work?Support cases under the subscription terms.Design, upgrade planning, recovery testing and tuning with written findings; 24/7 support if you add it.
Who fixes product defects?MariaDB, for products under subscription.We reproduce the defect and work it with you; defects needing a change to MariaDB's code stay upstream.
How is it bought?No public price; request a quote.Consulting quoted per engagement; support $24,000 to $72,000 a year (USD), set by SLA, scope and deployment.

For the release lines and their dates, read MariaDB end of life dates.

Not sure which option fits? A senior MariaDB engineer will scope it with you.

Contact Us

One partner, not five

We Support Your Entire Tech Stack

MariaDB rarely fails in isolation. AceMQ covers the full surrounding infrastructure — so one team owns the whole path instead of pointing at each other.

See all the technologies we supportShow fewer

What is included

What a MariaDB consulting engagement includes, and what it does not

Each row names one area of work. The right column is what stays outside the engagement.

MariaDB consulting scope: what is included and what is not, by area
AreaIncludedNot included
ReviewTopology and node count, gcache and flow control, GTID and replication state, slow queries and InnoDB sizing, and a ranked fix listRewriting your application's SQL beyond what a plan needs
Galera and MaxScaleQuorum and arbitrator design, SST method, routing, lag limits and failover, with drills and a runbookNetwork faults outside your estate
UpgradesPath from 10.x to 10.11, 11.4, 11.8 or 12.3, optimizer comparison, rolling upgrade rehearsal and rollbackDefects needing a change to MariaDB's code
Backup and recoverymariadb-backup runs checked, a timed restore to a scratch server and binary log replay to a chosen timeRunning your production backups, unless you add managed support
MySQL and MariaDB movesSQL, replication and client compatibility tests, parallel running and cutoverLicence advice

Pricing

How MariaDB consulting is priced

MariaDB consulting is quoted per engagement. A health check is a fixed scope; upgrade, migration and design work is scoped after the review so the quote matches the estate. A quote request is answered within 1 hour.

If you want 24/7 cover as well, the published range for AceMQ support is $24,000 to $72,000 a year (USD), set by SLA, scope and deployment. See MariaDB support.

Fit

Who MariaDB consulting from AceMQ is not for

  • You want the vendor's own Enterprise subscription terms changed; that is between you and MariaDB.
  • You need a fully managed database service run entirely off your infrastructure; consulting does not replace it.
  • You run a single small MariaDB with no replication and nothing due to change.

FAQs

MariaDB Questions Answered

Answers on MariaDB consulting from AceMQ: what is included, what breaks in an 11.x upgrade, how it differs from MySQL and how a restore is timed.

Still have questions about MariaDB? Email an Expert

What does MariaDB consulting include?

A health check of topology, Galera, replication, queries and backups, upgrade planning, Galera and MaxScale design, backup and recovery testing, and MySQL and MariaDB moves, each with written findings and a rollback plan.

Who offers MariaDB consulting and professional services?

MariaDB plc sells subscriptions and services around its Enterprise products, and independent firms such as AceMQ consult on Community and Enterprise Server, Galera and MaxScale, with the same engineers who work the 24/7 support rota.

What breaks in a 10.x to 11.x upgrade?

Optimizer and cost model behavior, client authentication and TLS defaults, and replication assumptions. We rehearse on a replica with real traffic and compare EXPLAIN FORMAT=JSON for the queries that matter.

How is MariaDB consulting different from MySQL consulting?

Galera, MaxScale, GTID semantics, storage engines such as Aria and MyRocks and the optimizer differ from MySQL. Advice written for MySQL is often wrong on MariaDB.

Can you move us between MySQL and MariaDB?

Yes, in either direction, after a compatibility test of SQL, replication format and client libraries, with parallel running and a rollback.

How long does a MariaDB restore take?

It depends on data size, storage and the backup method, and it is measured, not estimated: we restore your last backup to a scratch server and time it, then replay binary logs to a chosen point.

Can we work with AceMQ on MariaDB without a long contract?

Yes. AceMQ works on MariaDB in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual partner engagement that covers 24/7 support, proactive reviews and named engineers. Many teams start ad hoc and move to an annual partnership once the first engagement is done.

How much does AceMQ MariaDB support or consulting cost?

Every AceMQ proposal is tailored to your requirements: your MariaDB environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how MariaDB is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.

Let's talk

Time Your Restore Before You Need It

Describe your cluster layout and MariaDB version. We reply to quote requests within 1 hour.

A senior AceMQ engineer, not a sales queueAbout your MariaDB estate, not a pitch deckQuote requests answered within 1 hour

Production incident right now?Email a MariaDB Architect

Get in Touch

Talk to a MariaDB Expert

Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.

305-204-2607
info@acemq.com
66 W. Flagler St. 9th Floor
Miami, FL 33130

Prefer to talk now? Call us directly or use the consultation tab to find a time that works.

We respond within 1 hour.

Pick a time that works — no pressure, no pitch. Just 30 minutes with an expert.

We respond within 1 hour.