Migration sequencing
Release plans where schema and code steps interlock without a downtime window.
Deploy-safe schema flow
Expand-and-contract migration discipline for Laravel and raw SQL shops: every release ships schema that old and new code can both serve.
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
Release plans where schema and code steps interlock without a downtime window.
Batched, throttled backfills that respect replica lag and never block live writes.
Additive → transition → contract stages documented per change, with rollback per stage.
Migrations exercised in CI against production-like data volumes and lock budgets.
Execution path
Audit current migration practices and lock risks
Design the expand-contract sequence for pending changes
Implement backfill and verification tooling
Run the sequence on the next release with live metrics
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
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.
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.
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.
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
Tell us what is slow — CPU, queries, migrations, or cost — and we will scope the smallest safe fix.