When we reach for it
Existing MySQL estates, and clients whose hosting, tooling and operational knowledge are already built around it.
MySQL engineering
A widely deployed relational database, extremely well understood operationally, and the store underneath a large share of the applications we inherit.
When we would argue against it
We would not choose it over PostgreSQL for new work — the type handling, extension ecosystem and planner are behind — but a working, well-run MySQL database is not a reason to schedule a migration.
What it looks like in delivery
Schema and index work, replication and backup verification, and the careful upgrades that get an old instance onto a supported version without a maintenance window nobody can afford.
Where this appears on the site
Nothing on this site names it yet
We work in MySQL, and no case study or service page currently published on this site prints it in its stack. Rather than describe an engagement you cannot check, this space stays empty until one does. Ask us and we will talk you through it directly.
Also in data and storage
Working in MySQL?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.