A lot of working software runs on MySQL, and much of it has been running for years. I’ve built on it and maintained it across e-commerce platforms and business systems, and I’m happy to work on an established MySQL database rather than proposing you move off it.
What I’m usually asked to do
Most MySQL work that reaches me is one of three things: a database that has become slow as the business has grown, a schema that needs to change without downtime, or a migration onto managed hosting such as AWS RDS or Aurora.
All three are more about care than cleverness — reading the query plans, indexing what’s actually being queried, and making schema changes in versioned migrations that run as part of deployment rather than by hand on a Friday.
That last part is what keeps this kind of work predictable. A schema change that runs as part of your normal deployment is a change you can schedule, rather than an evening someone has to be available for.
If you’re starting something new I’d generally suggest PostgreSQL instead. If you already run MySQL, that’s rarely a good enough reason to move, and I’ll tell you so.
MySQL work I’ve delivered
- LoveCrafts — MySQL behind a heavily customised Magento Enterprise e-commerce platform, and later a set of APIs and microservices.
- Bulb — MySQL alongside PostgreSQL on GCP.
- China Checkup — MySQL behind a custom Laravel e-commerce system, as sole developer.
Hire a freelance MySQL developer
Contact me about your MySQL database or the application on top of it.