Why Database Sharding Needs a Routing Layer

Most teams treat sharding as a storage problem, but the real bottleneck is the routing layer that decides which shard handles each query. In this episode, Lucas and Luna break down why a naive hash on user ID breaks as soon as you add nodes, why consistent hashing became the default, and how Netflix's move to active-active sharding forced them to rethink routing entirely. They also look at Vitess, the project born from YouTube's scaling pain, and explain why routing tables and gossip protocols matter more than the shard key itself. If you've ever wondered why adding a shard can make everything slower before it gets faster, this conversation shows you the exact mechanism behind it. Plus, they discuss the trade-off between hot spots and query fan-out, and why some teams are now splitting read and write routing in the same database. This is a practical, no-nonsense look at the layer most people forget until it's too late.

#DatabaseSharding #RoutingLayer #ConsistentHashing #Vitess #Netflix #DistributedSystems #DataEngineering #DatabaseArchitecture #ScalingDatabases #ShardKey #HotSpots #QueryFanOut #GossipProtocol #ActiveActive #TechPodcast #FexingoBusiness #BusinessPodcast #DatabaseTech

Keep every episode free: buymeacoffee.com/fexingo