Why Tubi Chose Scala: A Backend Transformation Story
The article explains how Tubi, an ad‑supported streaming platform with tens of millions of users, migrated from a Node.js‑Spark‑Redis stack to a Scala‑based backend to achieve sub‑10‑millisecond recommendation latency, improve fault tolerance, and simplify domain modeling using Akka and functional programming.
Tubi is an ad‑supported streaming service owned by Fox, delivering over 40,000 movies and TV shows to more than 51 million monthly active users across multiple devices.
Its recommendation engine relies on machine‑learning algorithms that must process massive amounts of data quickly, requiring a highly efficient data‑processing pipeline.
Before adopting Scala, Tubi’s architecture combined a Node.js homepage service with Apache Spark‑based analytics and a Redis backend, making A/B testing cumbersome and slowing down feature delivery.
The company faced several challenges: high latency, limited fault tolerance, low throughput, technical debt, and the need for better observability and test coverage.
Switching to Scala allowed Tubi to model business domains more precisely, leverage the compiler for early error detection, and reduce the cost of evolving the system.
Scala’s powerful type system and the Akka actor framework enabled safe concurrent programming, fully utilizing multi‑core hardware and simplifying multi‑threaded code.
By combining object‑oriented and functional paradigms, Tubi built a high‑performance, scalable, and maintainable backend that cut recommendation latency from roughly 300 ms to about 10 ms.
The success has led Tubi to continue hiring senior Scala engineers to further improve low‑latency services, machine‑learning pipelines, and open‑source contributions.
Bitu Technology
Bitu Technology is the registered company of Tubi's China team. We are engineers passionate about leveraging advanced technology to improve lives, and we hope to use this channel to connect and advance together.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.