MySQL.
MySQL is a widely deployed open-source relational database, common in web applications and in estates built before PostgreSQL became a default. Most commercial MySQL work is operating and evolving an existing installation rather than choosing it for something new.
Where MySQL fits on a long engagement.
A long-running MySQL installation accumulates decisions: a replication topology someone set up years ago, a schema with columns nobody can explain, and a backup process whose restore path has never been tested. Establishing which of those is actually a risk is usually the first useful week of work.
Schema change is where MySQL estates hurt. Altering a large table can lock it, which on a live system means either a maintenance window or an online-change tool and a rehearsal. Teams that have not done it before tend to underestimate it exactly once.
What an assigned team does with MySQL.
Inherited MySQL is a knowledge problem more than a technical one. The topology, the failover behaviour and the reason a particular table has no foreign keys are all undocumented, and reconstructing that takes weeks the first time and zero the second — which only happens if the same person is still there.
The first work worth doing is almost never a feature. Proving a restore, understanding the replication lag and finding the queries that will fail at twice the volume are what protect everything assigned after them, and they sit under DevOps managed services as often as under data work.
What we use MySQL for.
- Testing the restore, not the backup Proving the recovery path works, which is a different exercise from confirming a backup file exists.
- Schema change without downtime Large table migrations planned and rehearsed rather than attempted during a release window.
- Read scaling Replicas and routing introduced deliberately, with the application aware of replication lag rather than surprised by it.
How MySQL capacity is assigned.
MySQL work is assigned under managed data services where the database is the constraint, or alongside backend capacity where the application is.
Tell us what your roadmap needs MySQL for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.