Why Your Database Needs a Concurrent Backup Strategy

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

Why Your Database Needs a Concurrent Backup Strategy

Listen for free

View show details

Episode 40 of Database Tech with Fexingo dives into the overlooked risks of database backups under concurrent workloads. Lucas explains how PostgreSQL's `pg_dump` can cause hidden performance degradation when run during peak hours, citing a real-world case where a fintech platform saw query latency spike 300% due to backup-induced lock contention. Luna brings up MySQL's Percona XtraBackup and the trade-offs between physical and logical backups. Together they explore why a concurrent backup strategy—using tools like `pg_basebackup` or WAL archiving—is critical for high-availability systems in mid-2026. Specific, actionable, and backed by numbers. #DatabaseBackups #ConcurrentBackups #PostgreSQL #MySQL #pg_dump #WALArchiving #PerconaXtraBackup #LockContention #HighAvailability #FintechCaseStudy #QueryLatency #BackupStrategy #DataEngineering #TechPodcast #DatabaseTechWithFexingo #FexingoBusiness #BusinessPodcast #ITOperations Keep every episode free: buymeacoffee.com/fexingo

No reviews yet