Why Database Compression Uses Dictionary Encoding Not Run-Length

Cloud storage costs jumped 15% this quarter, and database admins are feeling the heat. Lucas and Luna dive into one of the most underappreciated techniques for slashing storage bills: dictionary encoding. Using a real example from a user-activity table with a country column containing just 25 distinct values among 50 million rows, they show how mapping strings to integer codes can shrink that column by 10x. They compare dictionary encoding to run-length encoding and generic block compression, explaining why dictionaries win for columns with many repeated values but high cardinality columns need a different approach. Along the way, they discuss trade-offs like query decompression overhead and how adaptive dictionaries handle new values without rebuilding. This episode is essential listening for anyone managing large-scale OLAP workloads or trying to optimize cloud storage spend. The hosts also share how listener support keeps the show ad-free.

#DatabaseCompression #DictionaryEncoding #RunLengthEncoding #ColumnarStorage #DataStorage #CloudCosts #OLAP #QueryOptimization #StorageSavings #DatabaseInternals #FexingoBusiness #DatabaseTech #TechnologyPodcast #BusinessPodcast #DataEngineering #SQL #NoSQL #DataWarehousing

Keep every episode free: buymeacoffee.com/fexingo