Episodes

  • Why Your Database Triggers Are Slowing Everything Down

    Why Your Database Triggers Are Slowing Everything Down
    Jun 14 2026
    Lucas and Luna dive into the hidden performance cost of database triggers, using a real-world example from a mid-size e-commerce company that lost 40% of its checkout throughput due to a single poorly designed trigger. They explain why triggers break your ability to reason about latency, how they create hidden bottlenecks under write-heavy workloads, and what to use instead—like application-layer event handlers or queue-based processing. If you're a backend engineer or data architect who's ever added a trigger 'just to be safe,' this episode will make you think twice. #DatabaseTriggers #SQLPerformance #WriteHeavyWorkloads #BackendEngineering #DataArchitecture #DatabaseDesign #TechPodcast #DatabaseTech #FexingoBusiness #BusinessPodcast #Technology #DatabaseBottlenecks #Ecommerce #QueueBasedProcessing #EventDrivenArchitecture #ApplicationLayer #DatabaseLatency #TriggerOverhead Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    6 mins
  • Why Database Sharding Still Works in 2026

    Why Database Sharding Still Works in 2026
    Jun 14 2026
    In this episode of Database Tech with Fexingo, Lucas and Luna dive into the practical realities of database sharding in 2026. They use the example of a fast-growing e-commerce platform that split its order history across ten shards only to hit a cross-shard join nightmare. Lucas explains the difference between horizontal sharding and vertical partitioning, and why choosing the wrong shard key (user ID vs. order date) can destroy query performance. They discuss trade-offs between application-managed sharding and newer distributed SQL databases like CockroachDB and YugabyteDB. Luna brings up the hidden cost of resharding when data distribution skews. Specific benchmarks: how one mid-size fintech reduced p99 query latency from 600ms to 40ms after sharding by customer region. The episode also tackles the myth that sharding is obsolete thanks to NewSQL — and why smart engineers still reach for it when a single Postgres instance hits 4TB. No fluff, just practical data architecture. #DatabaseSharding #HorizontalPartitioning #ShardKey #CrossShardJoins #DistributedSQL #CockroachDB #YugabyteDB #Postgres #QueryPerformance #Latency #Resharding #DataSkew #NewSQL #TechPodcast #DatabaseTech #FexingoBusiness #BusinessPodcast #DataArchitecture Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    9 mins
  • Why Database Connection Pool Starvation Is Your Worst Nightmare

    Why Database Connection Pool Starvation Is Your Worst Nightmare
    Jun 13 2026
    Lucas and Luna dive into the mechanics and hidden costs of database connection pool starvation — a failure mode that can take down a production system in seconds. Using the real-world example of a mid-sized SaaS company that saw latency spike from 12ms to 22 seconds after a routine code deployment, they explain why connection pools are not a 'set and forget' resource. Lucas walks through the math: 50 connections in the pool, 50 concurrent queries, and a single slow query that blocks every other request. They discuss connection acquisition timeouts, queue depth, and the surprising fix — setting a max lifetime on connections to force periodic recycling. The conversation ends with a practical checklist: monitor pool usage, set `connectionTimeout` below 500ms, and always validate connections on checkout. If today's episode saves you one production incident, it's worth your time. #DatabasePerformance #ConnectionPooling #SQL #NoSQL #TechOps #ProductionIncident #ConnectionStarvation #PostgreSQL #MySQL #DatabaseOptimization #SaaS #BackendEngineering #Debugging #SoftwareEngineering #FexingoBusiness #BusinessPodcast #DatabaseTechWithFexingo #Technology Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    10 mins
  • Why Database Time Zone Handling Breaks Queries

    Why Database Time Zone Handling Breaks Queries
    Jun 13 2026
    In this episode of Database Tech with Fexingo, Lucas and Luna dive into the hidden chaos of time zone handling in databases. Using the real-world example of a popular booking platform that lost millions in revenue due to incorrect time zone conversions, they explore why most developers underestimate the complexity. They discuss the difference between TIMESTAMP WITH TIME ZONE and TIMESTAMP WITHOUT TIME ZONE in PostgreSQL, how indexing breaks when time zones shift, and why daylight saving time transitions cause silent data corruption. The episode also covers practical strategies like storing all timestamps in UTC at the database level, using application-layer time zone conversion, and the importance of testing edge cases like the 'spring forward' and 'fall back' moments. Listeners will learn one concrete lesson: always store timestamps in UTC and convert at query time—unless you want your midnight reports to include yesterday's data. #DatabaseTimeZones #SQLTimestamp #PostgreSQL #UTCDatabase #DaylightSavingTime #QueryPerformance #DataIntegrity #TimeZoneHandling #DatabaseDesign #TechPodcast #DatabaseTech #FexingoBusiness #BusinessPodcast #SoftwareEngineering #BackendDevelopment #DataEngineering #SQLTips #DatabaseOptimization Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    9 mins
  • Why Row-Oriented Storage Wastes Your Database SSD

    Why Row-Oriented Storage Wastes Your Database SSD
    Jun 12 2026
    Lucas and Luna dive into the hidden inefficiency of row-oriented storage for modern analytics workloads. They explain how columnar storage flips the script by storing data by column instead of row, dramatically reducing I/O and improving query speed. The episode uses a concrete example: a 50-column sales table where a typical dashboard query touches only 5 columns. Lucas walks through what happens on disk with a row store versus a column store, citing 10x compression gains and query speedups of 50x or more for aggregation-heavy queries. They also discuss real-world trade-offs, like slower single-row lookups and the rise of hybrid formats like Apache Parquet. Luna challenges Lucas on whether this is just for data warehouses or if it applies to transactional databases too. The episode is lively, specific, and leaves listeners with a clear mental model: row stores read entire rows even when you need one column; column stores read only the columns you ask for. #DatabaseStorage #ColumnarStorage #RowOriented #DataEngineering #SQL #NoSQL #ApacheParquet #QueryPerformance #DataCompression #Analytics #IOOptimization #TechPodcast #DatabaseTech #FexingoBusiness #BusinessPodcast #Technology #DataWarehouse #LucasAndLuna Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    11 mins
  • Why Database Connection Retry with Exponential Backoff Prevents Cascading Failures

    Why Database Connection Retry with Exponential Backoff Prevents Cascading Failures
    Jun 12 2026
    Lucas and Luna dive into a specific failure pattern that takes down production databases: the thundering herd problem caused by naive retry logic. They walk through a real-world example of a payment processing system where every failed connection retried immediately, and how switching to exponential backoff with jitter prevented cascading outages. They explain the math behind the backoff, why adding random jitter matters, and how tools like PostgreSQL's `pgBouncer` and application-level retry libraries implement this pattern. The episode also covers what happens when services don't coordinate retry windows. No fluff, just a concrete, actionable deep dive into one of the most overlooked database resilience patterns. #DatabaseRetryLogic #ExponentialBackoff #ThunderingHerd #CascadingFailure #PostgreSQL #pgBouncer #ConnectionRetry #DatabaseResilience #Jitter #RetryStrategy #DatabaseEngineering #BackendArchitecture #SystemDesign #FaultTolerance #ProductionOutage #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    9 mins
  • Why Database NULL Values Destroy Query Performance

    Why Database NULL Values Destroy Query Performance
    Jun 11 2026
    Episode 45 of Database Tech with Fexingo digs into a silent performance killer: how NULL values in your database columns can lead to full table scans, bloated indexes, and query plans that ignore your best indexes. Lucas and Luna walk through a real-world example from an e-commerce order database, showing how three-valued logic (TRUE, FALSE, UNKNOWN) confuses the query optimizer. They explain why 'WHERE amount > 100' might not return rows with NULL amounts, why indexes on nullable columns can be partially useless, and how NOT IN subqueries with NULLs can return zero rows even when data exists. They cover concrete fixes: using NOT NULL constraints, COALESCE defaults, filtered indexes, and IS NULL predicates. No theory without practice — this episode gives you one actionable tip: add a NOT NULL constraint to every column that should never be empty, and watch your query times drop. #DatabasePerformance #NULLValues #QueryOptimization #SQL #DatabaseIndexing #ThreeValuedLogic #DatabaseTips #TechPodcast #DataEngineering #DatabaseDesign #SQLPerformance #IndexTuning #DatabaseMistakes #Technology #FexingoBusiness #BusinessPodcast #DatabaseTech #LucasAndLuna Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    8 mins
  • Why Database Partition Pruning Fails Without Careful Design

    Why Database Partition Pruning Fails Without Careful Design
    Jun 11 2026
    Episode 44 of Database Tech with Fexingo: Lucas and Luna dig into a subtle performance killer in partitioned databases — partition pruning that silently doesn't prune. They walk through how a real-world e-commerce system ran full-table scans on 200 partitions because the WHERE clause used a function-wrapped partition key. They explain how databases like PostgreSQL and MySQL handle partition elimination, why DATE() on a timestamp column defeats it, and the one index trick that can backfire. Listeners learn how to audit their own queries for accidental full scans, and why a seemingly clean schema can hide a 100x performance gap. This episode is for engineers who think their partitioned tables are fast — but haven't checked the query plan lately. #DatabasePartitioning #PartitionPruning #SQLPerformance #QueryOptimization #PostgreSQL #MySQL #DatabaseDesign #TechPodcast #DatabaseTechWithFexingo #DataEngineering #PerformanceTuning #Indexing #DatabaseInternals #FexingoBusiness #BusinessPodcast #Technology #SoftwareEngineering #BackendDev Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    9 mins