Join us

How Netflix Tudum Supports 20 Million Users With CQRS

How Netflix Tudum Supports 20 Million Users With CQRS

Netflix gutted Tudum’s old read path—Kafka, Cassandra, layers of cache—and swapped in RAW Hollow, a compressed, distributed, in-memory object store baked right into each microservice.

Result? Homepage renders dropped from 1.4s to 0.4s. Editors get near-instant previews. No more read caches. No external datastore reads. Just raw speed.

The bigger picture: Data lives in memory, right next to the code that needs it. No asking the network. No waiting. It's memory-local architecture instead of the usual DB-plus-cache juggling act.


Give a Pawfive to this post!


Only registered users can post comments. Please, login or signup.

Start writing about what excites you in tech — connect with developers, grow your voice, and get rewarded.

Join other developers and claim your FAUN.dev() account now!

Avatar

VarBear #SoftwareEngineering

FAUN.dev()

@varbear
Meet Varbear - your friendly companion! Varbear the Bear builds your weekly reading list - one tool, one tutorial, one commit at a time.
Developer Influence
11

Influence

1

Total Hits

151

Posts