All articles

Operations

Cutting Database Costs Without Cutting Performance

Nov 11, 2026 cost optimization · right-sizing · archiving · cloud

Instance right-sizing, index pruning, and data lifecycle design — a savings playbook measured against latency, not hope.

Database bills grow for measurable reasons: instances sized for last year's worst moment, indexes nobody queries, and tables that accumulate history forever. Every one of those is reversible — and every reduction can be validated with latency measurements before it lands.

Find the indexes nobody uses

Every index is a write-time tax and a buffer-pool squatter. MySQL's sys.schema_unused_indexes and PostgreSQL's pg_stat_user_indexes make the waste visible. Drop candidates after a full business cycle of observation — then watch write latency improve along with the bill.

Right-size from measured utilization

Downsizing decisions from peak marketing numbers produce outages. Downsize from p95 utilization over a representative window, with headroom for growth. The instance two sizes smaller than the fear-driven one often costs 40% less and performs identically.

Tags

cost optimization right-sizing archiving cloud

Related articles

Work with Burj

Your database deserves engineering, not guesswork.

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

Plan an engagement