June 4, 2026

Multi-CDN and The Chaos Of Global Streaming, with Simon Ouderkirk

Apple Podcasts podcast player badge
Overcast podcast player badge
YouTube podcast player badge
Spotify podcast player badge
Amazon Music podcast player badge
Audible podcast player badge
RSS Feed podcast player badge
Podcast Addict podcast player badge
Castbox podcast player badge
Apple Podcasts podcast player iconOvercast podcast player iconYouTube podcast player iconSpotify podcast player iconAmazon Music podcast player iconAudible podcast player iconRSS Feed podcast player iconPodcast Addict podcast player iconCastbox podcast player icon

Matt Levine chats with Simon Ouderkirk, the VP of Product at Hydrolix, a streaming data lake built for log-intensive workloads that combines real-time and historical analytics at massive scale. They explore the hidden complexity of global content delivery, from multi-CDN architectures to the trade-offs between cost, reliability, and observability. Simon breaks down why perfect content delivery is impossible in real-world systems and how teams should design for failure rather than assume stability. He explains the rising importance of multi-CDN strategies, not just for resilience but also for cost dynamics and vendor incentives.

  • Simon explains what most people fundamentally get wrong about running infrastructure at scale in companies like Disney. He highlights how complex global delivery becomes when you’re serving hundreds of millions of users across multiple continents and device types. At that scale, even basic assumptions about reliability start to break.
  • Matt covers why content delivery is inherently imperfect in large-scale systems. He argues that if your entire architecture depends on perfect delivery, then it is already misaligned with reality. Real-world systems must assume failure and design around it.
  • Matt and Simon agree that single-CDN setups are operationally simple and easy to reason about. The complexity only emerges when you introduce multiple vendors and suddenly need to identify failures across systems. Without strong observability and governance, teams quickly become paralyzed.
  • Simon explains why relying on a single CDN creates a dependency risk that many teams underestimate. When all traffic flows through one provider, you are fully exposed to their reliability limits. Multi-CDN strategies introduce redundancy and increase system resilience.
  • Simon covers why cost, not just reliability, drives multi-CDN adoption. He points out that incentives between vendors and buyers are often misaligned in how performance data is shared. Observability platforms exist because no CDN fully exposes cross-system traffic truth.
  • Simon explains that both CDNs and customers ultimately want the same outcome: smooth, high-quality content delivery. But incentive structures mean vendors optimize for their slice of the system, not the full end-to-end experience. That gap creates the need for independent measurement layers.
  • Simon breaks down how value in live streaming is not evenly distributed over time. Some moments, like casual viewing, can tolerate delays without impact. But high-stakes live events demand real-time delivery where even seconds of buffering change the experience completely.
  • Matt explains why buying in larger volumes often improves pricing across industries, including CDN services. He challenges the assumption that simply adding more vendors automatically creates better pricing power. In many cases, long-term commitment delivers more leverage than fragmentation.
  • Simon explains that large-scale content delivery forces teams to accept imperfect measurement systems. When systems operate globally, even small degradations become significant in aggregate. Any metric that involves sampling or retention trade-offs inevitably simplifies reality.
  • Simon asks how data is shaping or reshaping the perception of end-user experience over time. He suggests that what teams choose to measure strongly determines what they prioritize. In practice, measurement becomes management.
  • Simon explains that the way companies think about data retention and measurement has changed significantly in the last five years. Trade-offs that once made sense may no longer apply in today’s environment. Updating those assumptions is not a correction of past mistakes but an adaptation to new realities.
  • Simon critiques the tendency of companies to justify layoffs purely through AI adoption. He argues that replacing people entirely instead of redeploying expertise reflects a lack of strategic creativity. The better path is using tools to amplify human capability, not eliminate it.
  • Simon explains that computers excel at repetitive, structured tasks that should be automated. Humans, however, bring deep domain expertise, judgment, and creativity that machines cannot replicate. The best systems combine both rather than replacing one with the other.
  • Simon notes that CDN businesses are increasingly shifting toward customer-centric models. He highlights the ongoing tension between building in-house systems and buying external solutions. The real challenge is deciding where excellence is required versus where “good enough” is acceptable.
  • Simon reveals that a significant portion of internet traffic is now generated by bots and non-human agents. This shift forces a rethink of how systems are designed and optimized. Interfaces and delivery systems must now account for both human and machine consumption patterns.
  • Simon reflects on how uncertain the current tech landscape has become. The foundational assumptions about how value is created and delivered are being re-evaluated in real time. This creates both risk and opportunity for companies trying to adapt.
  • Matt explains that the most important human value is shifting from knowledge to meaning-making. Information itself is increasingly automated and commoditized. What remains uniquely human is the ability to connect ideas into narratives that create insight.
  • Matt and Simon discuss whether multi-CDN strategies are genuinely strategic or simply unnecessarily complex. Simon suggests the answer is not binary and depends on execution quality. A poorly designed multi-CDN system can be worse than a well-run single-CDN setup.
  • Simon concludes that end users do not care about infrastructure choices like single or multi-CDN. If content fails to load, users blame the service, not the underlying architecture. Ultimately, responsibility sits with the product owner, not the vendor stack.

Simon Ourderkirk on LinkedIn

Hydrolix.io

theanycast.com/s3e6