Bird
0
0

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📝 Analysis Q13 of 15
Microservices - Real-World Architecture Case Studies
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?
AThe playlist service waits for the user to refresh the app manually
BThe playlist service directly modifies the recommendation service's database
CThe playlist service sends the request to the user interface to update
DThe playlist service updates its database and sends a message to the recommendation service
Step-by-Step Solution
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]
Quick Trick: 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

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes