CASE STUDY / 03
A production migration with a way back.
Primary executor of a database and storage modernization, rehearsed against restored production data with mirrored storage and explicit rollback paths.
Production delivery
Rails / PostgreSQL / S3 · confidential client
The problem
A Rails platform needed coordinated database, storage, and backup changes ahead of a high-risk production release.
My decision & contribution
I executed staging rehearsal, production-data restore, PostgreSQL upgrades, backup verification, and the storage cutover. Mirrored storage allowed a transition before switching to S3; application-level checks verified behavior.
The result
The production upgrade and cutover completed with less than one hour of customer-visible downtime and no known migration failure. This demonstrates a PostgreSQL/storage modernization, rather than a Rails major-version upgrade or measured recovery-time objective.