Measure before touching
Baselines, digest rankings, and EXPLAIN plans precede every change recommendation.
About Burj
Burj sits at the intersection of database engineering and production operations.
Our position
Every user-visible slowdown traces back to signals the database already emits: digest tables, lock graphs, plan changes, buffer misses. Burj reads those signals first, then changes the smallest thing that moves the metric.
Our scope covers production MySQL and PostgreSQL across engines, managed clouds, caching, and observability — delivered with rollback paths your team can execute, and documentation they can keep.
Burj references third-party platforms, engines, and tools by name to describe what we work with. Those names remain trademarks of their respective owners and do not imply affiliation, partnership, or endorsement.
Working principles
Baselines, digest rankings, and EXPLAIN plans precede every change recommendation.
Every plan states what it changes, what it could break, and how to reverse it.
Changes are validated against production-shaped data before production sees them.
Before/after metrics are locked into monitoring so the gains outlast the engagement.
Where we focus
MySQL 8, Percona Server, MariaDB — tuning, replication, and lock discipline.
Autovacuum, planner statistics, connection pooling, and bloat control.
RDS, Aurora, and managed services tuned to their operating constraints.
The monitoring and guardrails that keep performance honest over time.
Work with Burj
Tell us what is slow — CPU, queries, migrations, or cost — and we will scope the smallest safe fix.