Why Netflix Removed Kafka from Tudum’s Architecture

The new architecture embedded RAW Hollow directly into Tudum’s microservices, drastically simplifying the stack.
Image by Nalini Nirad
Netflix launched Tudum in 2021, promising fans a richer experience, exclusive behind-the-scenes footage, first looks, interviews, and more. Named after the iconic Netflix startup sound ‘tudum’, the official fan destination attracts over 20 million users each month, the company revealed.  Tudum is not just a blog; it is a high-performance publishing platform. However, behind the scenes, Netflix engineers were fighting the latency issue caused by a distributed, eventually consistent architecture. Initially built on a Command Query Responsibility Segregation (CQRS) model with Apache Kafka, Tudum’s setup favoured scale over speed. But when editors had to wait minutes to preview a change, the trade-off no longer made sense. The company decided to migrate it to its in-house tech
Subscribe or log in to Continue Reading

Uncompromising innovation. Timeless influence. Your support powers the future of independent tech journalism.

Already have an account? Sign In.

📣 Want to advertise in AIM? Book here

Picture of Ankush Das
Ankush Das
I am a tech aficionado and a computer science graduate with a keen interest in AI, Coding, Open Source, Global SaaS, and Cloud. Have a tip? Reach out to ankush.das@aimmediahouse.com
Related Posts
AIM Print and TV
Don’t Miss the Next Big Shift in AI.
Get one year subscription for ₹5999
Download the easiest way to
stay informed