Personalization at Spotify using Cassandra

This post details the architecture and technical decisions behind Spotify's personalization system, specifically highlighting the use of Cassandra for storing user profile attributes and entity metadata. It explains the rationale for choosing Cassandra, focusing on its ability to scale horizontally, support cross-site replication, provide low-latency operations with tunable consistency, and facilitate bulk data transfer from Hadoop. The post also outlines the overall system architecture, including the roles of Kafka, Storm, and Crunch, and discusses the evolution of the Cassandra data model for entity metadata and user profiles.