Why Database Sharding Still Works in 2026

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 Database Sharding Still Works in 2026

Listen for free

View show details

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

No reviews yet