Problem Statement: A Feed-First Audio Distribution Network
Frames podcast hosting as an open-protocol distribution problem where RSS is the contract, not a UI detail.
Problem statement
Design a podcast hosting platform where creators upload audio episodes, the platform stores and processes them, generates standards-compliant RSS feeds consumed by Apple Podcasts, Spotify, Overcast, Pocket Casts, and thousands of other apps, serves the audio at global scale through CDNs, measures every download and partial listen, optionally inserts ads dynamically, and supports paid or private episodes.
The defining constraint is that podcasting is an open protocol business. The RSS feed is the API of the entire industry: any app on earth can poll it, parse it, and fetch the enclosure URL. Once an episode URL is published, we lose control of who fetches it, when, how many times, and with what Range header. The platform must therefore be correct under adversarial polling, viral spikes, byte-range resumption, and third-party caching, while remaining cheap enough that hosting a show with a small audience is economically viable.
Why the problem is distinctive
A video platform controls its own player and can use manifest-based streaming end to end. A podcast host serves two fundamentally different consumption models at once: the download model, where a third-party app fetches an MP3 over plain HTTP with Range requests, guided by an XML document we do not control the rendering of; and the streaming model, where our own or partner apps stream audio and can report fine-grained consumption. Measurement must reconcile both. Monetization must work in both: baked-in ads for the download world, server-side dynamic ad insertion for the streaming world.
Public operating baseline
The category is large and publicly documented. Apple announced in June 2021 that Apple Podcasts had surpassed 2 million shows and 28 million episodes. Spotify reported 602 million monthly active users in Q4 2023 and has said the majority of new podcasts created on its platform originate from its Anchor creator tooling, which it acquired in February 2019 for a reported ~$150 million. The IAB measured US podcast advertising revenue at $1.83 billion in 2022, up from $1.45 billion in 2021. Edison Research's Infinite Dial 2023 reported about 42% of Americans aged 12+ listened to a podcast in the past month. These are cited public figures for context, not our design targets.
The four architectural planes
- Creation plane: upload, audio processing, metadata, entitlements, publish workflow.
- Distribution plane: RSS generation and delivery, audio delivery over multi-CDN, conditional requests, signed URLs.
- Measurement plane: download attribution, streaming consumption, rollups, creator dashboards, advertiser reporting.
- Monetization plane: ad decisioning, dynamic insertion, campaign pacing, billing.
A strong answer keeps these planes separate. Distribution must never block on measurement. Measurement must never block playback. Monetization must degrade without harming playback. The feed contract is versioned and immutable per render, because the entire external ecosystem caches it.
Key Highlights
- •RSS is the industry API: the feed and enclosure URLs are public contracts cached by thousands of third-party apps.
- •Two delivery models coexist: third-party download over plain HTTP, and first-party streaming with consumption telemetry.
- •Apple reported 2M+ shows and 28M+ episodes in 2021; IAB reported $1.83B US podcast ad revenue in 2022.
- •Four planes: creation, distribution, measurement, monetization — each degrades independently.
- •Once an enclosure URL is published, traffic is adversarial: spikes, Range requests, and bot crawls are normal.
Section Rescue Kit
Buzzwords to use:
Safe statements:
- "Let me separate what we control, the feed and the audio, from what we do not, the thousands of apps that poll and cache them."
- "Before choosing any technology, I will define the delivery contract with the open podcast ecosystem."