Deploy-safe schema flow

Zero-Downtime Migration Pipelines

Expand-and-contract migration discipline for Laravel and raw SQL shops: every release ships schema that old and new code can both serve.

Discuss your workload

Diagnosis context

Downtime is usually manufactured: a migration that locks tables while the app serves them, a column rename that breaks the running release, a backfill that saturates I/O. Expand-and-contract removes the manufacturing: additive changes first, dual-write and dual-read in transition, cleanup later — each step reversible and traffic-safe.

What the fix plan covers

Every intervention is reversible and measured.

01

Migration sequencing

Release plans where schema and code steps interlock without a downtime window.

02

Backfill discipline

Batched, throttled backfills that respect replica lag and never block live writes.

03

Expand-contract playbook

Additive → transition → contract stages documented per change, with rollback per stage.

04

CI verification

Migrations exercised in CI against production-like data volumes and lock budgets.

Execution path

From live diagnosis to a measured, reversible fix.

  1. 01

    Audit current migration practices and lock risks

  2. 02

    Design the expand-contract sequence for pending changes

  3. 03

    Implement backfill and verification tooling

  4. 04

    Run the sequence on the next release with live metrics

  5. 05

    Codify the playbook into your team's process

Measured outcome

A schema pipeline your team can deploy on a Friday — because it never locks the live system.

Common Questions

What engineering teams ask before working with us.

Our MySQL sits at 100% CPU right now. How fast can you help?

Emergency engagements start with a live diagnostic session — processlist sampling, digest analysis, and parameter review. Stabilization typically lands within one engagement day, with the root cause documented and a monitoring hook to catch recurrence.

Can a large ALTER really run without downtime?

Yes, when the strategy matches the change. Instant DDL covers many column operations in MySQL 8; in-place operations fit others; and gh-ost or pt-online-schema-change handle the rest with throttling tied to replica lag. We classify every change before anyone runs it, then rehearse on a production-size replica.

We keep getting deadlocks on the same tables. Is this a code problem?

It is an ordering problem, and the fix usually spans both sides. We map the lock graph and specify the transaction re-sequencing your team applies — typically a small, single-commit change. Isolation levels and index design, which are database-side, do most of the heavy lifting.

Why is our JSON-heavy API so slow?

Because queries filtering or sorting on JSON paths scan without an index. The fix keeps your flexible schema: virtual generated columns over the hot paths, indexes on those columns, and predicate rewrites at the database layer. Your application continues reading the same JSON.

Work with Burj

Bring your worst database incident to Burj.

Tell us what is slow — CPU, queries, migrations, or cost — and we will scope the smallest safe fix.

Plan an engagement