Path inventory
Every JSON path used in filters, sorts, and joins — inventoried from live queries, not guesses.
Virtual columns + indexes
Your JSONB/JSON columns stay flexible; we add virtual columns and generated indexes so the hot paths inside them stop scanning.
Diagnosis context
Semi-structured columns earn their place — until someone filters on them. A JSON field used in WHERE or ORDER BY without an index forces full scans and I/O spikes. The fix keeps your schema: generated virtual columns over the queried paths, indexes on those columns, and rewritten predicates that the optimizer can actually use.
What the fix plan covers
Every JSON path used in filters, sorts, and joins — inventoried from live queries, not guesses.
Generated columns typed and named so the optimizer uses them without touching your app.
Multi-valued and functional indexes where MySQL and PostgreSQL versions support them.
JSON_EXTRACT → virtual column swaps applied at the database layer, no application diff.
Execution path
Mine live queries for JSON path usage
Design virtual columns and candidate indexes
Validate plans on staging with production-size data
Deploy columns and indexes online
Re-verify latency on the affected endpoints
Measured outcome
Flexible JSON storage with indexed-path performance — no application changes required.
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.