Virtual columns + indexes

JSON Columns That Finally Perform

Your JSONB/JSON columns stay flexible; we add virtual columns and generated indexes so the hot paths inside them stop scanning.

Discuss your workload

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 intervention is reversible and measured.

01

Path inventory

Every JSON path used in filters, sorts, and joins — inventoried from live queries, not guesses.

02

Virtual column design

Generated columns typed and named so the optimizer uses them without touching your app.

03

Index selection

Multi-valued and functional indexes where MySQL and PostgreSQL versions support them.

04

Predicate rewrites

JSON_EXTRACT → virtual column swaps applied at the database layer, no application diff.

Execution path

From live diagnosis to a measured, reversible fix.

  1. 01

    Mine live queries for JSON path usage

  2. 02

    Design virtual columns and candidate indexes

  3. 03

    Validate plans on staging with production-size data

  4. 04

    Deploy columns and indexes online

  5. 05

    Re-verify latency on the affected endpoints

Measured outcome

Flexible JSON storage with indexed-path performance — no application changes required.

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