Netflix Tudum Architecture: from CQRS with Kafka to CQRS with RAW Hollow
Netflix's Tudum platform transitioned from a CQRS architecture with Kafka to using RAW Hollow, enhancing data propagation speed, reducing latency, and improving user experience by leveraging in-memory caching and strong read-after-write consistency.
MAIN POINTS
- Tudum.com is Netflix’s fan destination offering exclusive content and interactive experiences.
- Initial architecture used CQRS with Kafka, causing delays in content updates due to eventual consistency.
- RAW Hollow, an in-memory database, improved data access speed and reduced architecture complexity.
- Migration to RAW Hollow decreased homepage construction time from ~1.4 seconds to ~0.4 seconds.
TAKEAWAYS
- CQRS can scale well but may introduce delays due to eventual consistency.
- In-memory caching with RAW Hollow significantly reduces I/O and improves performance.
- Eliminating sequential operations can greatly enhance response times.
- RAW Hollow allows for efficient dataset management with strong read-after-write consistency.