Projects
Chained database projects: model the data, pipe real data into it, then tune it under load.
High-Availability Replication + Failover — Full Technical Writeup
The complete technical record, in the order it actually happened: GTID-based replication from scratch, a first failover attempt that surfaced real gaps and was deliberately paused, then a completed drill and a genuine multi-app production incident. Every command below actually ran.
Cross-Database / Cloud Migration (CDC, Near-Zero Downtime)
Built and verified a real Debezium/Kafka Connect CDC pipeline streaming project1_jobs from self-hosted MySQL to self-hosted Postgres, zero lag, row counts matched. This is the CDC piece only — the other 9 app databases, the actual cutover, and any cloud target are deliberately not done yet.
Data Governance & Security (Masking, RBAC, Audit Logging)
Add role-based access control, PII column masking, and audit logging to an existing schema — and specifically, instrument the `portfolio_admin` write-path built earlier this session (2026-08-18) with real audit logging, so the project is partly about auditing this portfolio's own system rather than only a synthetic exercise.
Automated, Tested Backup/DR Pipeline
Turn Project 3's manual `mysqldump --single-transaction | gzip` runbook into a scheduled, automated pipeline with retention policy and — critically — automated, *tested* restores, not just backups that are assumed to work.
Production Monitoring & Alerting
This is the detailed technical record in the same style as the replication project's writeup: every command and query actually run, every issue actually hit, and how each was actually resolved — including a real cascading connection-exhaustion incident during the final verification step, kept in full because it's stronger evidence than a clean scripted test would have been.
DBA: Performance Tuning at Scale
Load the schema with a million synthetic rows and run a full slow-query diagnosis and tuning case study.