Workspace

Dashboard Learn Handbook Labs Practice library Learning paths Review Insights Studios Mock interviews Notebook

Personal workspace · self-hosted

Search

Jump to a problem, path or page

Music Streaming Service · Decisions · designlab

Dashboard Learn Handbook Labs Practice library Learning paths Review Insights Studios Mock interviews Notebook

Search

Jump to a problem, path or page

Library ArchitectureMusic Streaming Service

♫

Music Streaming Service

HLDIntermediate45 minCaching & delivery Storage & partitioning Data pipelines & analytics Guided lab

All changes saved Not started

Choose the policy you would defend in a design review. Choices save as you go.

Where should audio bytes be served from?

1.Where should audio bytes be served from?

Streamed through the API servers from the databaseFrom a CDN backed by object storageRe-encoded on every request

How should play events be recorded?

2.How should play events be recorded?

Synchronously in the metadata database before playback startsOnly in the client, uploaded once a monthAppended to an event stream that workers aggregate asynchronously

What makes a play countable for royalties?

3.What makes a play countable for royalties?

A deduplicated event with a play id, listened past a thresholdAny request for the audio fileA row in the playlist table

Trade-offs, failure cases and tests

Explain a rejected alternative, a failure mode and how you would test the design. At least 80 characters for the completeness check.

0 characters

Review my design