Design Music Licensing System - System Design | WinJob

Design Music Licensing System — Problem Statement

Music licensing is the financial and legal control plane behind streaming: it turns billions of play events into correct royalty allocations for songwriters, publishers, labels, and collecting societies — while respecting territory windows, contract types, and dispute holds.

Companies like Spotify, YouTube, and SoundExchange ask this to test whether you can separate high-volume playback telemetry from slow, auditable royalty settlement — rights graphs, split snapshots, and PRO filings are not the same problem as audio CDN delivery.

Who cares

Actor	Goal
Listener	Stream any licensed track in their region
Rights holder	Accurate statements, timely payouts, dispute resolution
Platform	Legal compliance, predictable royalty expense
Label / publisher	Windowing, minimum guarantees, audit trail

Core journeys

Listener → platform: play track → client reports qualified listen (30s rule) → usage event emitted with ISRC + territory.

Platform → rights holders: aggregate plays → apply pool model → allocate splits → generate statements → pay via ACH/wire/PRO.

Rights admin: ingest contract → map ISRC to split graph → territory rules → freeze at settlement close.

javaOne Dark Pro

1 public record PlayEvent(String idempotencyKey, String isrc, String territory, long listenedMs) {
2   public boolean billable(long minMs) { return listenedMs >= minMs; }
3 }

pythonOne Dark Pro

1 from dataclasses import dataclass
2  
3 @dataclass(frozen=True)
4 class PlayEvent:
5     idempotency_key: str
6     isrc: str
7     territory: str
8     listened_ms: int
9  
10     def billable(self, min_ms: int) -> bool:
11         return self.listened_ms >= min_ms

typescriptOne Dark Pro

1 interface PlayEvent {
2   idempotencyKey: string;
3   isrc: string;
4   territory: string;
5   listenedMs: number;
6 }
7  
8 function isBillable(event: PlayEvent, minMs: number): boolean {
9   return event.listenedMs >= minMs;
10 }

Extended interview notes

Problem Statement & Music Licensing Context note 1: Rights graph links ISRC/ISWC to writers, publishers, and labels with territory-specific shares. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 2: Play events are append-only with idempotency keys — replays must not inflate royalties. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 3: Mechanical vs performance vs sync rights use different pools and settlement calendars. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 4: Territory evaluation runs at play time using geo-IP + contract windows, not catalog ingest only. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 5: Royalty allocation uses pro-rata pool by default; user-centric is a product toggle with cost. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 6: SoundExchange-style statutory rates differ from label direct deals — model both contract types. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 7: Dispute workflow freezes splits until claim resolution; never pay conflicting parties. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 8: Warehouse holds raw plays; OLTP ledger holds aggregated payable lines only. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 9: Play events are append-only with idempotency keys — replays must not inflate royalties. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 10: Mechanical vs performance vs sync rights use different pools and settlement calendars. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 11: Territory evaluation runs at play time using geo-IP + contract windows, not catalog ingest only. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 12: Royalty allocation uses pro-rata pool by default; user-centric is a product toggle with cost. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 13: SoundExchange-style statutory rates differ from label direct deals — model both contract types. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 14: Dispute workflow freezes splits until claim resolution; never pay conflicting parties. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 15: Warehouse holds raw plays; OLTP ledger holds aggregated payable lines only. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 16: Rights graph links ISRC/ISWC to writers, publishers, and labels with territory-specific shares. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 17: Play events are append-only with idempotency keys — replays must not inflate royalties. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 18: Mechanical vs performance vs sync rights use different pools and settlement calendars. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 19: Territory evaluation runs at play time using geo-IP + contract windows, not catalog ingest only. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 20: Royalty allocation uses pro-rata pool by default; user-centric is a product toggle with cost. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 21: SoundExchange-style statutory rates differ from label direct deals — model both contract types. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 22: Dispute workflow freezes splits until claim resolution; never pay conflicting parties. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 23: Warehouse holds raw plays; OLTP ledger holds aggregated payable lines only. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 24: Rights graph links ISRC/ISWC to writers, publishers, and labels with territory-specific shares. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 25: Play events are append-only with idempotency keys — replays must not inflate royalties. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 26: Mechanical vs performance vs sync rights use different pools and settlement calendars. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 27: Territory evaluation runs at play time using geo-IP + contract windows, not catalog ingest only. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).
Problem Statement & Music Licensing Context note 28: Royalty allocation uses pro-rata pool by default; user-centric is a product toggle with cost. Tie SLIs to allocation accuracy (zero duplicate pay), statement freshness (<48h post-close), and rights lookup p99 (<20ms).

Why interviewers care

Music Licensing System interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

Interview checkpoint

Name one failure story for Problem Statement & Music Licensing Context that proves you understand real outages, not happy-path diagrams.

Key Highlights

•Problem Statement & Music Licensing Context: music licensing focus
•ISRC-keyed idempotent play pipeline
•Split snapshots at settlement close

1	public record PlayEvent(String idempotencyKey, String isrc, String territory, long listenedMs) {
2	public boolean billable(long minMs) { return listenedMs >= minMs; }
3	}

1	from dataclasses import dataclass
2
3	@dataclass(frozen=True)
4	class PlayEvent:
5	idempotency_key: str
6	isrc: str
7	territory: str
8	listened_ms: int
9
10	def billable(self, min_ms: int) -> bool:
11	return self.listened_ms >= min_ms

1	interface PlayEvent {
2	idempotencyKey: string;
3	isrc: string;
4	territory: string;
5	listenedMs: number;
6	}
7
8	function isBillable(event: PlayEvent, minMs: number): boolean {
9	return event.listenedMs >= minMs;
10	}