71:{"json":{"id":"seed_8e3a3afe7054014a9db88a17e7dd7ffb","slug":"spotify-music-streaming","category":"System Design","topic":"Spotify Music Streaming","title":"Designing Spotify: Music Streaming at Scale","description":"Master the architecture of a global music streaming platform. Learn how to design systems for audio streaming, playlist management, recommendations, offline mode, and handle licensing complexities—serving hundreds of millions of users worldwide.","difficulty":"ADVANCED","estimatedMinutes":180,"pages":[{"id":"seed_7da971520cc223fc9afb3b1eea4d8750","title":"Requirements: Streaming and Playlists","order":0,"content":[{"id":"opening-context","title":"Designing the Soundtrack of Modern Life","content":[{"data":{"content":"**Spotify** is more than a music player—it's a distributed system that streams over **100 million songs** to **615+ million users** across **180+ markets** worldwide. Every day, users generate billions of streams, create millions of playlists, and interact with an ever-growing catalog of audio content. Behind the simple act of pressing 'play' lies one of the most sophisticated content delivery systems ever built.\n\nDesigning a system like Spotify requires balancing seemingly contradictory requirements: **instant playback** with **global reach**, **personalized experiences** with **massive scale**, and **seamless streaming** with **complex licensing constraints**. This case study explores how to architect such a system from first principles."},"type":"text"},{"data":{"icon":"Target","title":"What You Will Learn","content":"By the end of this page, you will understand how to gather and analyze requirements for a music streaming platform, distinguish between functional and non-functional requirements, and establish the scope and scale that will drive every architectural decision throughout this design.","variant":"info"},"type":"callout"}]},{"id":"problem-space","title":"Understanding the Problem Space","content":[{"data":{"content":"Before diving into architecture, we must deeply understand what we're building. A music streaming platform operates at the intersection of **content delivery**, **personalization**, **social features**, and **licensing compliance**. Each dimension introduces unique challenges that cascade through every layer of the system.\n\n**The core problem statement:**\n\n> Design a system that allows users to discover, stream, and organize music from a catalog of 100+ million tracks, with sub-second playback latency, support for hundreds of millions of concurrent users, and compliance with complex licensing agreements across 180+ countries.\n\nLet's break this down systematically."},"type":"text"},{"data":{"items":["**Content Management** — How do we ingest, process, store, and serve a catalog of 100+ million audio files efficiently?","**Streaming Delivery** — How do we deliver audio with minimal latency to users anywhere in the world, adapting to varying network conditions?","**User Experience** — How do we enable playlist creation, library management, and music organization at scale?","**Personalization** — How do we recommend music tailored to individual tastes from a catalog of millions?","**Cross-Device Continuity** — How do we enable users to seamlessly transition between devices without losing their session?","**Offline Access** — How do we allow users to download and play music without network connectivity?","**Licensing Compliance** — How do we enforce geo-restrictions and licensing rules that vary by country and label?"],"title":{"icon":"Layers","text":"Problem Dimensions","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"icon":"Info","title":"Scope for This Case Study","content":"We'll focus on the core streaming and playlist functionality first, then progressively address recommendations, offline mode, and licensing in subsequent pages. This mirrors how you would approach a system design interview—start with the core, then expand based on time and interviewer interest.","variant":"note"},"type":"callout"}],"titleType":"number","titleNumber":1},{"id":"scale-constraints","title":"Scale and Constraints","content":[{"data":{"content":"Understanding scale is critical—it determines whether your design works in production or collapses under load. Let's quantify the scale we're designing for:\n\n**User Scale:**\n- **615+ million** monthly active users (MAU)\n- **250+ million** paid subscribers (Premium users)\n- **100+ million** concurrent users during peak hours\n- Users spread across **180+ countries** and every timezone\n\n**Content Scale:**\n- **100+ million tracks** in the catalog\n- **5+ million podcast episodes** (podcasts increasingly important)\n- **4+ billion playlists** user-created\n- **40,000+ new tracks** added daily\n\n**Usage Patterns:**\n- Average user streams **148 minutes per day**\n- **70% of listening** happens on mobile devices\n- **300+ million hours** of music streamed daily"},"type":"text"},{"data":{"rows":[["Daily Streams","615M users × 50% DAU × 30 songs/day","~9 billion streams/day","Need massively parallel streaming infrastructure"],["Peak QPS for Streams","9B / 86,400 × peak multiplier (3x)","~312,500 streams/second","Requires distributed architecture across regions"],["Storage (Original)","100M tracks × 50MB avg (lossless)","~5 PB raw storage","Object storage with efficient encoding"],["Storage (Encoded)","100M × 5 qualities × 10MB avg","~5 PB encoded","Plus redundancy = 15+ PB total"],["Metadata Volume","100M tracks × 5KB metadata avg","~500 GB","Fits in memory with sharding"],["Playlist Data","4B playlists × 100 tracks × 50 bytes","~20 TB playlist data","Sharded database cluster"]],"caption":"Back-of-Envelope Calculations","headers":["Metric","Calculation","Result","Implications"]},"type":"table"},{"data":{"icon":"AlertCircle","title":"Scale Shapes Architecture","content":"At hundreds of thousands of streams per second, every architectural decision compounds. A 1ms latency increase affects 300+ million streams daily. A 1% error rate means 90 million failed streams per day. These numbers drive our obsession with efficiency and reliability.","variant":"warning"},"type":"callout"}],"titleType":"number","titleNumber":2},{"id":"functional-streaming","title":"Functional Requirements: Audio Streaming","content":[{"data":{"content":"The core functionality of any music streaming platform is, of course, streaming audio. But this simple concept expands into numerous specific requirements when we examine it closely.\n\n**Core Streaming Requirements:**"},"type":"text"},{"data":{"items":["**Instant Playback** — Music must begin playing within 200ms of pressing play. Users expect immediate response.","**Continuous Streaming** — Once started, playback must continue without interruption. Buffer underruns cause audio glitches that destroy user experience.","**Adaptive Quality** — Stream quality must adjust dynamically based on network conditions. Seamless quality transitions without audible artifacts.","**Multiple Bitrates** — Support for quality ranging from 24kbps (low quality mobile) to 320kbps (Premium) to lossless (HiFi).","**Gapless Playback** — Tracks that are meant to flow into each other (albums, DJ sets) must play without silence gaps.","**Crossfade** — Optional crossfade between tracks for DJ-like listening experience."],"title":{"icon":"Play","text":"Audio Playback","type":"icon","color":"primary","variant":"outline-circle"},"variant":"glass"},"type":"list"},{"data":{"items":["**Loudness Normalization** — Tracks from different albums/eras should play at consistent perceived volume levels.","**Audio Effects** — Support for equalizer settings that users can customize.","**High-Quality Audio** — For premium tiers, support lossless audio (FLAC, 24-bit).","**Mono/Stereo Detection** — Properly handle both mono historical recordings and modern stereo.","**Format Support** — Handle various source formats from labels (WAV, FLAC, MP3, AAC, Ogg)."],"title":{"icon":"Volume2","text":"Audio Quality & Processing","type":"icon","color":"secondary","variant":"outline-circle"},"variant":"glass"},"type":"list"},{"data":{"content":"**Playback Control Requirements:**"},"type":"text"},{"data":{"items":["**Play/Pause** — Immediate response to play and pause commands.","**Skip Forward/Back** — Jump to next/previous track in queue.","**Seek** — Scrub to any position within a track with minimal delay.","**Shuffle** — Play tracks from a playlist in random order (with smart shuffle avoiding repetition).","**Repeat** — Repeat single track, entire playlist, or disable repeat.","**Queue Management** — Add tracks to queue, reorder queue, clear queue.","**Recently Played** — Track and display listening history."],"title":{"icon":"SkipForward","text":"Playback Controls","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"icon":"Lightbulb","title":"Interview Strategy","content":"When gathering streaming requirements in an interview, always ask about: quality tiers, network conditions to handle, mobile vs. desktop differences, and whether gapless/crossfade is needed. These determine encoding strategy and buffer management.","variant":"tip"},"type":"callout"}],"titleType":"number","titleNumber":3},{"id":"functional-playlists","title":"Functional Requirements: Playlists & Library","content":[{"data":{"content":"Playlists are the organizational backbone of music streaming. They represent how users curate, organize, and share their music. Spotify hosts over **4 billion playlists**, making playlist management a core architectural challenge.\n\n**Playlist Management Requirements:**"},"type":"text"},{"data":{"items":["**Create Playlist** — Users can create unlimited playlists with custom names and descriptions.","**Add Tracks** — Add individual tracks or bulk-add from albums, artists, or other playlists.","**Remove Tracks** — Remove tracks from any position without reordering delays.","**Reorder Tracks** — Drag-and-drop reordering with immediate persistence.","**Delete Playlist** — Permanently remove playlists (with potential soft-delete for recovery).","**Duplicate Playlist** — Copy existing playlist as starting point for new one."],"title":{"icon":"ListMusic","text":"Playlist CRUD Operations","type":"icon","color":"primary","variant":"outline-circle"},"variant":"glass"},"type":"list"},{"data":{"items":["**Public/Private Toggle** — Control visibility of playlists to other users.","**Shareable Links** — Generate links that allow others to view or follow playlists.","**Collaborative Playlists** — Multiple users can add/remove tracks from shared playlists.","**Follow Playlists** — Subscribe to playlists created by others to see updates.","**Playlist Folders** — Organize playlists into hierarchical folder structures."],"title":{"icon":"Share2","text":"Playlist Sharing & Collaboration","type":"icon","color":"secondary","variant":"outline-circle"},"variant":"glass"},"type":"list"},{"data":{"content":"**User Library Requirements:**\n\nBeyond playlists, users maintain a personal library of saved content:"},"type":"text"},{"data":{"items":["**Liked Songs** — A special system playlist of all tracks the user has 'hearted'.","**Saved Albums** — Full albums saved for quick access.","**Followed Artists** — Artists the user follows for new release notifications.","**Saved Podcasts/Episodes** — For podcast functionality.","**Listening History** — Recently played tracks, albums, and playlists.","**Your Library** — Unified view of all saved content across types."],"title":{"icon":"Library","text":"Personal Library","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"rows":[["Total Playlists","4+ billion","Storage and indexing","Sharded databases with playlist_id partitioning"],["Tracks per Playlist","Up to 10,000","Large playlist rendering","Virtualized lists, paginated fetches"],["Collaborative Edits","Concurrent writes","Conflict resolution","CRDT-like merge strategies"],["Playlist Follows","Millions per popular playlist","Fan-out updates","Eventual consistency, notifications batching"],["Search within Playlist","Large playlists","Client-side performance","Server-side search for 500+ tracks"]],"caption":"Playlist Scale Challenges","headers":["Feature","Scale","Challenge","Approach"]},"type":"table"},{"data":{"icon":"Info","title":"Playlist Data Model Complexity","content":"Playlists seem simple but involve complex data relationships: owner, collaborators, followers, track ordering, track metadata snapshots (what if a track is later removed from catalog?), and version history for rollback. We'll design this data model carefully in the architecture section.","variant":"note"},"type":"callout"}],"titleType":"number","titleNumber":4},{"id":"functional-discovery","title":"Functional Requirements: Discovery & Search","content":[{"data":{"content":"Users need to find music, whether they know exactly what they want or are exploring for something new. Discovery encompasses both explicit search and algorithmic recommendations.\n\n**Search Requirements:**"},"type":"text"},{"data":{"items":["**Multi-Entity Search** — Search across tracks, artists, albums, playlists, podcasts, and users simultaneously.","**Instant Results** — Results appear as user types (typeahead with <100ms latency).","**Fuzzy Matching** — Handle typos, partial matches, and phonetic similarities.","**Relevance Ranking** — Results ordered by relevance considering popularity, user history, and query match.","**Filters** — Filter by content type, genre, release year, etc.","**Browse by Genre/Mood** — Pre-categorized discovery paths."],"title":{"icon":"Search","text":"Search Functionality","type":"icon","color":"primary","variant":"outline-circle"},"variant":"glass"},"type":"list"},{"data":{"content":"**Content Browsing:**"},"type":"text"},{"data":{"items":["**Artist Pages** — Complete artist information: discography, top tracks, about, concert tickets, merch.","**Album Pages** — Track listing, release info, credits, related albums.","**Genre/Mood Hubs** — Curated collections of playlists and albums by category.","**New Releases** — Latest releases relevant to user's taste.","**Charts** — Top 50 by country, global charts, viral charts.","**Curated Playlists** — Editorially curated playlists like 'RapCaviar', 'Today's Top Hits'."],"title":{"icon":"Compass","text":"Browsing & Navigation","type":"icon","color":"secondary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"icon":"Lightbulb","title":"Search vs. Recommendations","content":"Search is explicit intent—the user knows what they want. Recommendations address implicit discovery—helping users find music they'll love but don't know about yet. Both require different architectural approaches: search needs full-text indexing, while recommendations need ML pipelines and feature stores.","variant":"tip"},"type":"callout"}],"titleType":"number","titleNumber":5},{"id":"non-functional-requirements","title":"Non-Functional Requirements","content":[{"data":{"content":"Non-functional requirements define *how well* the system must perform, not *what* it does. For a music streaming platform, these requirements are often more challenging than the functional ones.\n\n**Performance Requirements:**"},"type":"text"},{"data":{"rows":[["Time to First Byte","<200ms globally","Users expect instant playback"],["Buffering Ratio","<1% of playback time","Buffering destroys listening experience"],["Search Latency","<100ms for typeahead","Results must appear while typing"],["API Latency (P99)","<500ms","UI responsiveness depends on quick API calls"],["Playlist Load Time","<300ms for 1000 tracks","Large playlists must render quickly"],["Cold Start Time","<3s on mobile","App must be usable within seconds"]],"caption":"Performance SLAs","headers":["Metric","Target","Rationale"]},"type":"table"},{"data":{"content":"**Scalability Requirements:**"},"type":"text"},{"data":{"items":["**Horizontal Scalability** — System must scale to handle 2x current load by adding resources, not redesigning.","**Geographic Distribution** — Support users across 180+ countries with acceptable latency (<200ms to nearest edge).","**Peak Load Handling** — Handle 3x average load during major events (album drops, New Year's Eve).","**Catalog Growth** — Support 40,000+ new tracks daily without reindexing delays.","**User Growth** — Architecture must support billion-user scale within 3-5 years."],"title":{"icon":"TrendingUp","text":"Scalability Targets","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"content":"**Availability & Reliability:**"},"type":"text"},{"data":{"items":["**Availability SLA** — 99.95% uptime (≈22 minutes downtime/month). Premium subscribers expect near-perfect availability.","**Stream Reliability** — 99.99% of started streams complete without failures.","**Data Durability** — Zero tolerance for playlist or library data loss. 99.999999999% (11 nines) durability.","**Graceful Degradation** — When components fail, degrade gracefully (e.g., no recommendations is better than no playback).","**Regional Failover** — Single region failure must not impact users in other regions."],"title":{"icon":"Shield","text":"Reliability Targets","type":"icon","color":"secondary","variant":"outline-circle"},"variant":"glass"},"type":"list"},{"data":{"icon":"AlertCircle","title":"The Cost of Streaming Failures","content":"A music streaming failure is immediately perceived—unlike background sync or email, users experience disruption in real-time. A 1-minute global outage during peak hours affects 100+ million active listeners. This drives extreme reliability requirements.","variant":"warning"},"type":"callout"}],"titleType":"number","titleNumber":6},{"id":"additional-nfr","title":"Security, Compliance & Operational Requirements","content":[{"data":{"content":"**Security Requirements:**"},"type":"text"},{"data":{"items":["**Content Protection** — Audio streams must be protected against unauthorized copying (DRM for premium content).","**Authentication** — Secure login with support for social auth, SSO, and 2FA.","**Authorization** — Ensure users can only access content they're entitled to (subscription tier, geo-availability).","**Privacy** — Protect user listening data; comply with GDPR, CCPA for data access/deletion requests.","**Account Security** — Detect and prevent account sharing abuse (contractual limits on simultaneous streams).","**Fraud Prevention** — Detect artificial streaming (click farms) that manipulate royalty payouts."],"title":{"icon":"Lock","text":"Security Considerations","type":"icon","color":"destructive","variant":"outline-circle"},"variant":"glass"},"type":"list"},{"data":{"content":"**Compliance Requirements:**\n\nMusic streaming is heavily regulated through licensing agreements:"},"type":"text"},{"data":{"items":["**Geo-Restrictions** — Certain tracks available only in specific countries based on licensing deals.","**Royalty Tracking** — Every stream must be tracked accurately for royalty calculations.","**Content Takedown** — Ability to immediately remove content upon rights holder request.","**Play Limits** — Some content has play limits for free tier (e.g., skips per hour).","**Explicit Content** — Filter and warn for explicit content based on user settings."],"title":{"icon":"FileCheck","text":"Licensing Compliance","type":"icon","color":"primary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"content":"**Operational Requirements:**"},"type":"text"},{"data":{"items":["**Monitoring** — Real-time visibility into streaming health, error rates, and latencies worldwide.","**Alerting** — Immediate notification of anomalies (spike in errors, latency degradation).","**Logging** — Structured logs for debugging with appropriate retention and privacy masking.","**Tracing** — Distributed tracing across services to diagnose complex failures.","**Feature Flags** — Gradual rollout of features with ability to quickly disable.","**Blue-Green Deployments** — Zero-downtime deployments with instant rollback capability."],"title":{"icon":"Settings","text":"Operations & Observability","type":"icon","color":"secondary","variant":"outline-circle"},"variant":"glass"},"type":"list"}],"titleType":"number","titleNumber":7},{"id":"prioritizing-requirements","title":"Prioritizing Requirements for MVP","content":[{"data":{"content":"In a system design interview, you cannot address every requirement in depth. Strategic prioritization demonstrates maturity. Here's how to think about priorities for a music streaming MVP:\n\n**P0 (Must Have) — Without these, no viable product:**"},"type":"text"},{"data":{"type":"ordered","items":["**Audio streaming** — Core value proposition. Must work reliably.","**Search** — Users need to find music to play.","**User accounts** — Needed for personalization, playlists, subscriptions.","**Basic playlist management** — Create, add tracks, play playlist.","**Catalog metadata** — Track, album, artist information must be available."],"title":{"icon":"AlertCircle","text":"Critical Requirements","type":"icon","color":"destructive","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"content":"**P1 (Important) — Needed for competitive product:**"},"type":"text"},{"data":{"items":["**Personalized recommendations** — Key differentiator for retention.","**Adaptive bitrate streaming** — Essential for mobile users.","**Cross-device sync** — Users expect seamless device switching.","**Offline mode** — Critical for commuters and travelers.","**Social features** — Following friends, sharing playlists."],"title":{"icon":"Star","text":"Important Requirements","type":"icon","color":"primary","variant":"outline-circle"},"variant":"glass"},"type":"list"},{"data":{"content":"**P2 (Nice to Have) — Enhancements for mature product:**"},"type":"text"},{"data":{"items":["**Lyrics display** — Popular but not critical.","**Collaborative playlists** — Social feature enhancement.","**Podcasts** — Separate content type with different characteristics.","**Concert integration** — Ticketing, artist events.","**High-fidelity audio** — Niche premium feature."],"title":{"icon":"Sparkles","text":"Enhancement Features","type":"icon","color":"secondary","variant":"outline-circle"},"variant":"accent"},"type":"list"},{"data":{"icon":"Lightbulb","title":"Interview Prioritization","content":"In an interview, explicitly state your prioritization: 'I'll focus on P0 requirements first—streaming, search, and basic playlists. Once we have a solid architecture for those, we can discuss how to add recommendations and offline mode.' This shows maturity and time management.","variant":"tip"},"type":"callout"}],"titleType":"number","titleNumber":8},{"id":"requirements-summary","title":"Requirements Summary","content":[{"data":{"content":"We've established a comprehensive understanding of what we're building. Let's consolidate the key requirements that will drive our architecture:"},"type":"text"},{"data":{"rows":[["Streaming","Instant playback (<200ms), adaptive quality, gapless playback","P0"],["Playlists","Create/manage playlists, add/remove/reorder tracks, sharing","P0"],["Search","Multi-entity search with <100ms typeahead latency","P0"],["Library","Save songs, albums, artists; sync across devices","P0/P1"],["Recommendations","Personalized discovery based on listening history","P1"],["Offline Mode","Download and play without network connectivity","P1"],["Performance","<200ms time to first byte, <1% buffering ratio","P0"],["Availability","99.95% uptime, graceful degradation","P0"],["Compliance","Geo-restrictions, royalty tracking, DRM","P0"]],"caption":"Requirements Summary","headers":["Category","Key Requirements","Priority"]},"type":"table"},{"data":{"content":"**What's next:**\n\nWith requirements established, we'll move into the architectural design. The next page covers **Audio Streaming Architecture**—how we encode, store, distribute, and deliver audio content to hundreds of millions of users with sub-second latency. This is the technical heart of the system."},"type":"text"},{"data":{"icon":"CheckCircle","title":"Page Complete","content":"You now have a comprehensive understanding of the requirements for designing a music streaming platform like Spotify. We've covered functional requirements (streaming, playlists, search), non-functional requirements (performance, scale, reliability), and established clear priorities for MVP development. Next, we dive into the architecture that makes streaming possible at global scale.","variant":"success"},"type":"callout"}],"titleType":"number","titleNumber":9}],"isLocked":false},{"id":"seed_9f676c313e7e0e572fcdf81a2e2b2224","title":"Audio Streaming Architecture","order":1,"content":null,"isLocked":true},{"id":"seed_62e05b6c455c686b95e2c1901e70cc77","title":"Playlist and Library Management","order":2,"content":null,"isLocked":true},{"id":"seed_7112cb7424445768051a15180ab0009b","title":"Recommendation System","order":3,"content":null,"isLocked":true},{"id":"seed_8e2f1e41d3a1a8eff40137a0730e95e2","title":"Offline Mode","order":4,"content":null,"isLocked":true},{"id":"seed_24c037f7dafd1018a787049661893049","title":"Licensing and Geo-Restrictions","order":5,"content":null,"isLocked":true}]}}