Spotify architecture overview in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Identify the core components in Spotify's microservices architecture

Spotify uses a microservices architecture to handle music streaming, user management, and recommendations. Which of the following lists the main microservices correctly?

A User Service, Music Catalog Service, Recommendation Service, Playback Service

B User Interface Service, Payment Gateway, Music Storage Service, Analytics Service

C Authentication Service, Video Streaming Service, Playlist Service, Notification Service

D Search Service, Email Service, Social Media Service, Billing Service

💡 Hint

Think about services that handle users, music data, recommendations, and playing songs.

Spotify's microservices include User Service for user data, Music Catalog Service for music metadata, Recommendation Service for personalized suggestions, and Playback Service for streaming music.

❓ scaling

intermediate

Scaling the Playback Service for millions of users

Spotify's Playback Service must handle millions of concurrent streams. Which approach best supports this scale?

A Store all music files in a single database and stream directly from it

B Use a single powerful server to handle all playback requests to reduce complexity

C Deploy multiple instances of Playback Service behind a load balancer and use CDN for content delivery

D Send playback requests to the User Service to manage streaming

💡 Hint

Think about distributing load and reducing latency for users worldwide.

Deploying multiple Playback Service instances behind a load balancer allows handling many users. Using a CDN caches music close to users, reducing latency and load on origin servers.

❓ tradeoff

advanced

Choosing between synchronous and asynchronous communication

Spotify's Recommendation Service needs data from User Service and Music Catalog Service. What is a key tradeoff when choosing synchronous vs asynchronous communication between these services?

A Synchronous calls provide immediate data but can cause delays if services are slow; asynchronous calls improve resilience but add complexity

B Asynchronous calls require no error handling; synchronous calls require complex error handling

C Synchronous calls always improve performance; asynchronous calls always reduce data accuracy

D Synchronous calls are cheaper to implement; asynchronous calls require expensive hardware

💡 Hint

Consider response time and system reliability.

Synchronous communication waits for immediate responses, which can slow down if a service is slow or down. Asynchronous communication decouples services, improving resilience but making data handling more complex.

🧠 Conceptual

advanced

Understanding data storage choices in Spotify architecture

Spotify stores user playlists, music metadata, and playback history. Which storage types best fit these data categories?

A User playlists in cache only, music metadata in time-series database, playback history in NoSQL

B All data stored in a single relational database for simplicity

C User playlists in flat files, music metadata in NoSQL, playback history in relational database

D User playlists in a NoSQL database, music metadata in a relational database, playback history in a time-series database

💡 Hint

Think about data structure and query patterns for each data type.

User playlists are flexible and fit well in NoSQL for quick access. Music metadata is structured and fits relational databases. Playback history is time-based, so time-series databases are ideal.

❓ estimation

expert

Estimating storage needs for Spotify's music catalog

Spotify has 100 million songs averaging 5 MB metadata each. Estimate the total storage needed for the music metadata database, considering 20% overhead for indexing and backups.

A 500 million MB (500 TB)

B 600 million MB (600 TB)

C 400 million MB (400 TB)

D 120 million MB (120 TB)

💡 Hint

Calculate base size then add 20% overhead.

Base size = 100 million songs * 5 MB = 500 million MB. Adding 20% overhead: 500 million * 1.2 = 600 million MB, which is 600 TB.

Practice

1. What is the main reason Spotify uses microservices in its architecture?

easy

A. To avoid using APIs between components

B. To separate different tasks for better scalability and maintenance

C. To make the app use less memory on devices

D. To reduce the number of servers needed

Solution

1. Step 1: Understand microservices purpose

   Microservices split an app into small parts, each handling a specific task.

2. Step 2: Connect to Spotify's needs

   Spotify uses this to make the app scalable and easier to maintain by isolating tasks.

3. Final Answer:

   To separate different tasks for better scalability and maintenance -> Option B

4. Quick Check:

   Microservices = Separate tasks for scalability [OK]

Hint: Microservices split tasks for easier scaling and updates [OK]

Common Mistakes:

• Thinking microservices reduce memory usage directly
• Believing microservices avoid APIs
• Assuming microservices reduce server count

2. Which communication method is commonly used between Spotify's microservices?

easy

A. APIs and message queues

B. FTP file transfers

C. Shared memory

D. Direct database access

Solution

1. Step 1: Identify common microservice communication

   Microservices usually communicate via APIs or message queues for loose coupling.

2. Step 2: Match with Spotify's design

   Spotify uses APIs and message queues to keep services independent and responsive.

3. Final Answer:

   APIs and message queues -> Option A

4. Quick Check:

   Microservices communicate via APIs/message queues [OK]

Hint: Microservices talk via APIs or message queues, not direct DB [OK]

Common Mistakes:

• Choosing direct database access which breaks service independence
• Selecting shared memory which is uncommon in distributed systems
• Picking FTP which is unrelated to microservice communication

3. Consider a microservice that handles user playlists. If it receives a request to add a song, what is the likely flow in Spotify's architecture?

medium

A. The playlist service waits for the user to refresh the app manually

B. The playlist service directly modifies the recommendation service's database

C. The playlist service sends the request to the user interface to update

D. The playlist service updates its database and sends a message to the recommendation service

Solution

1. Step 1: Understand service responsibilities

   The playlist service manages playlists and updates its own data store.

2. Step 2: Recognize inter-service communication

   After updating, it informs other services like recommendations via messages.

3. Final Answer:

   The playlist service updates its database and sends a message to the recommendation service -> Option D

4. Quick Check:

   Playlist service updates DB + notifies others [OK]

Hint: Services update own data, notify others via messages [OK]

Common Mistakes:

• Assuming direct DB access across services
• Thinking UI triggers backend updates
• Believing manual refresh is needed for updates

4. A developer notices that Spotify's microservices sometimes fail to update user data consistently. What is a likely cause in the architecture?

medium

A. APIs are synchronous, causing delays

B. Services are directly sharing the same database without coordination

C. Message queues are not used, causing lost updates

D. Microservices are deployed on the same server

Solution

1. Step 1: Identify cause of inconsistent updates

   Without message queues, updates may be lost or not delivered reliably.

2. Step 2: Understand Spotify's architecture best practices

   Spotify uses message queues to ensure reliable communication and consistency.

3. Final Answer:

   Message queues are not used, causing lost updates -> Option C

4. Quick Check:

   Missing message queues = lost updates [OK]

Hint: Lost updates often mean missing message queues [OK]

Common Mistakes:

• Blaming shared database without evidence
• Confusing synchronous APIs with update loss
• Assuming deployment location causes data inconsistency

5. Spotify wants to add a new feature that recommends songs based on live user activity. Which architectural change fits best with their microservices approach?

hard

A. Create a new recommendation microservice that consumes live activity events via message queues

B. Add the recommendation logic directly inside the user interface code

C. Store all live activity data in a single monolithic database accessed by all services

D. Use FTP to transfer live activity logs to the recommendation service hourly

Solution

1. Step 1: Identify best practice for new feature in microservices

   Adding a new microservice keeps responsibilities separate and scalable.

2. Step 2: Use message queues for live data

   Consuming live events via message queues fits asynchronous, decoupled design.

3. Final Answer:

   Create a new recommendation microservice that consumes live activity events via message queues -> Option A

4. Quick Check:

   New microservice + message queues = best fit [OK]

Hint: New features get own microservice, use message queues for live data [OK]

Common Mistakes:

• Embedding logic in UI breaks separation
• Using monolithic DB reduces scalability
• FTP is outdated and slow for live data