Cilantrobyte.

Tech Stacks · Data

MySQL

When the client already runs it and there's no good reason to migrate.

Category

Data

At the studio

Since 2019

Projects shipped

Numerous

Status

Active

(01) Our take

MySQL is a fine database. We wouldn't pick it for greenfield work over Postgres, but we won't push a migration on a client whose infrastructure is happy. We have the operational depth to run large MySQL clusters well, including with Planetscale and Vitess for horizontally sharded setups.

The cases where MySQL is genuinely preferable are narrower than its install base suggests — but they exist. If you need Vitess-scale sharding with battle-tested semantics, or if your hosting platform prices MySQL favourably, we'll work in it without complaint.

(02) What we build with it

Typical work

  • Feature work on existing MySQL-backed applications
  • WordPress and Laravel stacks that default to MySQL
  • Planetscale-hosted applications with Vitess sharding
  • MySQL-to-Postgres migration audits

(03) How we engage

Engagement shape

Almost always embedded in a larger backend engagement rather than standalone.

(04) Pairs with

Works well with

Technologies we reach for alongside MySQL in most engagements.

Data

PostgreSQL

The default database. For almost everything.

Backend

Laravel

When PHP is the right answer.

Commerce

WordPress

Still powering a third of the internet — and sometimes that's fine.

Backend

PHP

The foundation most of the internet still runs on.

Thinking about a MySQL project?

Start a project →back to all stacks