Spotify architecture overview in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main architectural style used by Spotify for its backend services?

Spotify uses a microservices architecture, where the system is divided into small, independent services that communicate over the network.

beginner

Why does Spotify use microservices instead of a monolithic architecture?

Microservices allow Spotify to develop, deploy, and scale different parts of the system independently, improving flexibility and reliability.

intermediate

What role does the 'Gateway' service play in Spotify's architecture?

The Gateway acts as a single entry point for client requests, routing them to the appropriate microservices and handling authentication and rate limiting.

intermediate

How does Spotify handle user data and playlists in its architecture?

User data and playlists are managed by dedicated microservices with their own databases, ensuring data isolation and easier scaling.

advanced

What is the purpose of the event-driven communication in Spotify's microservices?

Event-driven communication allows services to react to changes asynchronously, improving system responsiveness and decoupling services.

Which architectural style does Spotify primarily use for its backend?

A Microservices

B Monolithic

C Client-Server

D Peer-to-Peer

Spotify uses microservices to build scalable and independent backend services.

What is the main benefit of using a Gateway service in Spotify's architecture?

A Manages music streaming directly

B Stores all user data

C Handles database backups

D Single entry point for routing and security

The Gateway routes requests and manages authentication and rate limiting.

How does Spotify ensure that different parts of the system can scale independently?

A By using microservices with separate databases

B By using a single large database

C By deploying one big application

D By using peer-to-peer networking

Microservices with their own databases allow independent scaling.

What type of communication helps Spotify services react asynchronously to changes?

A Synchronous HTTP calls only

B Event-driven communication

C Direct database queries

D File sharing

Event-driven communication decouples services and improves responsiveness.

Which of these is NOT a typical responsibility of a Spotify microservice?

A Managing user playlists

B Streaming music content

C Handling client UI rendering

D Processing user authentication

Client UI rendering is done on the client side, not by backend microservices.

Explain the key components of Spotify's microservices architecture and how they interact.

Think about how small services work together and communicate.

Describe how Spotify manages scalability and reliability using its architecture.

Focus on how the system grows and stays stable.

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