EPISODE · Jun 4, 2026 · 8 MIN
How One Team Decided Their Database Was the Wrong Database
from Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations · host Fexingo
Episode 30 of Tech Leadership with Fexingo dives into the hardest infrastructure decision a CTO can face: when to migrate off a database that's been running in production for years. Lucas and Luna unpack the story of a mid-stage SaaS company that switched from MongoDB to PostgreSQL after three years of accumulating workarounds, query timeouts, and data inconsistency bugs. They walk through the technical triggers — specifically a cascading replica failure during a routine backup — that forced the engineering team to admit their document store was the wrong fit for their relational domain. The episode covers how the team sized the migration, why they chose a strangler fig pattern over a big-bang cutover, and the one metric that told them the migration had succeeded: p99 query latency dropped from 1.2 seconds to 40 milliseconds. No hype, no vendor pitches — just a real engineering leadership story about admitting a mistake and executing a fix at scale. #DatabaseMigration #MongoDBtoPostgreSQL #StranglerFigPattern #EngineeringLeadership #CTODecisions #Infrastructure #TechDebt #DataConsistency #QueryLatency #PostgreSQL #MongoDB #MigrationStrategy #ProductionIncident #SaaS #TechnicalLeadership #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo
What this episode covers
Episode 30 of Tech Leadership with Fexingo dives into the hardest infrastructure decision a CTO can face: when to migrate off a database that's been running in production for years. Lucas and Luna unpack the story of a mid-stage SaaS company that switched from MongoDB to PostgreSQL after three years of accumulating workarounds, query timeouts, and data inconsistency bugs. They walk through the technical triggers — specifically a cascading replica failure during a routine backup — that forced the engineering team to admit their document store was the wrong fit for their relational domain. The episode covers how the team sized the migration, why they chose a strangler fig pattern over a big-bang cutover, and the one metric that told them the migration had succeeded: p99 query latency dropped from 1.2 seconds to 40 milliseconds. No hype, no vendor pitches — just a real engineering leadership story about admitting a mistake and executing a fix at scale. #DatabaseMigration #MongoDBtoPostgreSQL #StranglerFigPattern #EngineeringLeadership #CTODecisions #Infrastructure #TechDebt #DataConsistency #QueryLatency #PostgreSQL #MongoDB #MigrationStrategy #ProductionIncident #SaaS #TechnicalLeadership #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo
NOW PLAYING
How One Team Decided Their Database Was the Wrong Database
No transcript for this episode yet
Similar Episodes
Mar 26, 2026 ·1m
Mar 19, 2026 ·34m
Feb 18, 2026 ·11m
Feb 11, 2026 ·45m