Indexing the Data Lake for Online Point Queries
- Source
- engineering.atspotify.com
- Author
- Spotify Engineering
- Date

Context
Spotify's Random Access Parquet approach makes a large analytical dataset usable for targeted lookups, such as retrieving one listener's history. An external index records which files and rows contain each key. Cached file metadata then identifies the relevant pages, allowing the reader to request those byte ranges directly. Spotify's engineering article explains how this avoids a chain of reads just to discover where the requested data lives.
The approach reuses the data lake's existing Parquet files, so a separate full serving copy is unnecessary. It still requires an index and its upkeep. Unmodified files may also require reading a large page for a small result; preparing the file layout can reduce that overhead.
articleAI Changed How Spotify Builds. What We Learned (and Fixed) About Quality at Higher Velocity- articleSpotify’s Backstage Portal cut my Claude Code token usage by 90%
articleCoding Is No Longer the Constraint: Scaling Developer Experience to Teams and Agents at Spotify
articleEncoding Your Domain Expert: The Context Layer Behind Spotify's Data Assistant
articleEncoding Your Domain Expert: The Context Layer Behind Spotify's Data AssistantSpotify Engineering
videoVertical Mobility: Inference from MVP to Trillion-Parameter Workloads — Sitanshu Gupta, CoreWeaveAI Engineer
videoServing 2 Million Models Without Melting: Scaling the Hugging Face Hub — Arek Borucki, Hugging FaceAI Engineer
Checking sign-in…
Loading comments…