About the service
I'm a database engineer, and I spend most of my time bringing MySQL and PostgreSQL into shape under real production load. Over the years I've inherited plenty of systems where one slow query could bring the whole app down, and I've learned: the answer is almost never just buying more hardware. I start with measurements — reading execution plans, checking the slow query log, looking at buffer pool and cache hits — and only then decide what really needs to change. That discipline keeps me from guessing and keeps your bills realistic.
Most of my work fits into a few areas. I rewrite heavy queries to touch fewer rows, design indexes based on how the app actually accesses data rather than indexing every column, and build replication schemes that give read scaling and hot standby without surprises during failover. I take backups seriously: that means testing recovery, not just putting a dump on a schedule and hoping. When a schema needs to change on a live table with millions of rows, I plan the migration to run online, in clear steps, with a rollback plan ready, so nobody holds their breath during deploy.
Clients appreciate that I explain tradeoffs in plain language and leave the database in a state their team can maintain themselves. I document what changed and why, and I happily work alongside your developers so the knowledge sticks.
— MySQL and PostgreSQL tuning and configuration
— Query optimization and execution plan analysis
— Index design and review, removing unused indexes
— Replication setup: streaming, logical, read replicas, failover
— Backup strategy and tested point-in-time recovery
— Safe online schema migrations with rollback plans
— Slow query diagnosis, deadlocks, and lock troubleshooting
— Capacity planning, monitoring, and alert configuration
Most of my work fits into a few areas. I rewrite heavy queries to touch fewer rows, design indexes based on how the app actually accesses data rather than indexing every column, and build replication schemes that give read scaling and hot standby without surprises during failover. I take backups seriously: that means testing recovery, not just putting a dump on a schedule and hoping. When a schema needs to change on a live table with millions of rows, I plan the migration to run online, in clear steps, with a rollback plan ready, so nobody holds their breath during deploy.
Clients appreciate that I explain tradeoffs in plain language and leave the database in a state their team can maintain themselves. I document what changed and why, and I happily work alongside your developers so the knowledge sticks.
— MySQL and PostgreSQL tuning and configuration
— Query optimization and execution plan analysis
— Index design and review, removing unused indexes
— Replication setup: streaming, logical, read replicas, failover
— Backup strategy and tested point-in-time recovery
— Safe online schema migrations with rollback plans
— Slow query diagnosis, deadlocks, and lock troubleshooting
— Capacity planning, monitoring, and alert configuration
