Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Platform Engineering Podcast

Platform Engineering Podcast artwork

Smart TV Testing Made Simple with Dave Lucia of TV Labs

Mar 19, 202548 minAudio
  • Apple Podcasts
ShareXLinkedInFacebookWhatsAppEmail

Testing smart TV applications presents unique challenges that traditional web testing approaches can't solve. Dave Lucia, CTO and co-founder of TV Labs, shares how his team built a platform that virtualizes televisions and set-top boxes to help media companies test their smart TV apps on physical devices. Learn about TV Labs' innovative architecture and how they handle everything from camera-based testing systems to their custom Lua-based DSL for faster test execution. A key highlight is how choosing Elixir as their primary technology has enabled TV Labs to build a robust orchestration system. The language's built-in capabilities for fault tolerance, process isolation, and distributed computing make it particularly well-suited for managing concurrent connections and real-time state across multiple devices. The discussion also explores practical insights about system architecture, including how TV Labs leverages Phoenix presence for real-time device state tracking and achieves microsecond-level performance for message broadcasting. Guest: Dave Lucia, CTO & Co-Founder at TV Labs Dave is a technology leader with deep experience designing and scaling systems across industries including media, sports betting, finance, and developer tooling. He is a prominent member of the BEAM community, regularly speaking at conferences such as Code BEAM SF, ElixirConf, The Big Elixir, and RabbitMQ Summit. Dave Lucia, Website Dave Lucia, X Dave Lucia. Bluesky TV Labs TV Labs, LinkedIn Links to interesting things from this episode: Appium “The Road to 2 Million Websocket Connections in Phoenix” “From $erverless to Elixir” eBPF

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Guests

  • Dave Lucia Guest Inferred

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Taking a Summer Break: What Would You Like To Hear This Fall?

    Jul 15, 20263 minAudio

    We're hitting pause for the summer on new episodes of the Platform Engineering Podcast, but don’t worry, we’ve got some great episodes in the feed to keep you entertained in the meantime. If you’ve got suggestions for...

    • Apple Podcasts

    Credit the people on this episode

  2. What Do Service Meshes Actually Solve? (William Morgan, Buoyant/Linkerd)

    Jun 24, 202656 minAudio

    Network calls fail in ways function calls never do - and once a monolith becomes microservices, reliability problems show up fast: retries amplify load, latency spikes cascade, and “what talks to what?” becomes hard to...

    • Apple Podcasts

    Credit the people on this episode

  3. Continuous Integration at Agentic Velocity with CircleCI’s Rob Zuber

    Jun 10, 202650 minAudio

    When code gets cheaper to produce, feedback becomes the limiting factor - CI, reviews, and the handoffs between tools can quietly slow everything down. Rob Zuber breaks down what platform engineers are seeing as teams...

    • Apple Podcasts

    Credit the people on this episode

  4. Durable Execution for Real‑World Failures with Temporal’s Cornelia Davis

    May 27, 202646 minAudio

    A lot of infrastructure and automation fails for ordinary reasons: rate limits, flaky networks, partial permissions, long-running jobs, and retries that vanish when the process restarts. Durable execution is a way to...

    • Apple Podcasts

    Credit the people on this episode

  5. You Need AI Sysadmins Can Trust, With Cribl's Nikhil Mungel

    May 13, 202655 minAudio

    What happens when a non-deterministic AI system is asked to touch production telemetry or generate changes for an SRE pipeline? The cost of being “close enough” can be lost data, downtime, or a security incident....

    • Apple Podcasts

    Credit the people on this episode