Slow queries, a messy schema, or two databases that need to become one? I design, migrate and tune PostgreSQL databases for production apps, and I've done it for healthcare and logistics systems where data integrity can't slip.
What I can do
Schema design and normalization for new or growing products
Database consolidation and data migration with full legacy-ID traceability
Safe migrations across foreign-key-heavy schemas, with rollback plans
Query and index tuning using EXPLAIN ANALYZE
PostGIS setup for location and geospatial data
AWS RDS setup, backups and environment refreshes (QA, staging, prod)
What you get
An audit with findings, migration scripts tested against a copy of your data, a written runbook, and a before/after performance report.
Recent work
Consolidated two PostgreSQL databases for a healthcare client into a single schema, preserving legacy IDs for traceability.
Slow queries, a messy schema, or two databases that need to become one? I design, migrate and tune PostgreSQL databases for production apps, and I've done it for healthcare and logistics systems where data integrity can't slip.
What I can do
Schema design and normalization for new or growing products
Database consolidation and data migration with full legacy-ID traceability
Safe migrations across foreign-key-heavy schemas, with rollback plans
Query and index tuning using EXPLAIN ANALYZE
PostGIS setup for location and geospatial data
AWS RDS setup, backups and environment refreshes (QA, staging, prod)
What you get
An audit with findings, migration scripts tested against a copy of your data, a written runbook, and a before/after performance report.
Recent work
Consolidated two PostgreSQL databases for a healthcare client into a single schema, preserving legacy IDs for traceability.