Browse past weeks of engineering reads.
Netflix engineers needed a real-time, unified view of service dependencies across their microservices architecture to enable faster troubleshooting and understand blast radius during incidents.
Netflix needed to generate personalized homepages at scale where every row, entity ordering, and layout element is customized per user while maintaining low latency and high relevance.
Preventing corrupted catalog metadata from reaching millions of Netflix viewers by detecting data transformation failures in production before impact.
How to design a notification system that intelligently decides when and how to deliver personalized notifications to users with varying urgency and cognitive load requirements.
Netflix needed to efficiently partition and manage petabytes of time series event data across Cassandra clusters while maintaining millisecond-level query latency and handling dynamic workload changes.
Netflix engineers lacked a real-time, comprehensive view of service dependencies and relationships across their distributed microservices infrastructure, making incident diagnosis and troubleshooting during outages significantly slower.
Netflix needed to predict and mitigate risks associated with content launches to improve reliability and reduce unexpected failures in production.
Netflix needed to design a personalized notification system that efficiently decides when and how to notify users with relevant content recommendations without overwhelming them or missing critical engagement opportunities.
Accurately measuring video quality perception to optimize encoding decisions and ensure Netflix members receive the best possible streaming experience across different bitrates and codecs.
Netflix needed to efficiently partition and scale time series data across Cassandra clusters to handle petabytes of temporal event data while maintaining millisecond latency query performance.
Netflix needed a real-time, dynamic way for engineers to understand service dependencies and troubleshoot issues quickly across their complex distributed microservices infrastructure.
Netflix needed to optimize bandwidth utilization and video quality for live streaming events at global scale by moving from constant bitrate to variable bitrate encoding.
Query performance degradation at massive scale (10+ trillion rows, 15M events/second) where repeated identical queries were consuming excessive resources and impacting latency.
Netflix needed to build reliable operations infrastructure to support live streaming at massive scale, going from one show per month to nine shows per day with tens of millions of concurrent viewers.
Delivering high-quality streaming video across diverse devices and varying network conditions requires efficient video encoding; legacy codecs like H.264 and VP9 were limiting compression efficiency, consuming more bandwidth for equivalent visual quality.
Netflix needed reliable orchestration for business-critical cloud operations across teams like Open Connect CDN and Live reliability, but faced operational challenges as Temporal adoption grew since 2021.
Netflix needed to spin up hundreds of containers in seconds to serve streaming traffic, but after modernizing their container runtime, they hit an unexpected performance bottleneck rooted in CPU architecture that impaired container scaling efficiency.
Netflix needed a custom origin server to bridge its cloud-based live streaming pipelines with its CDN (Open Connect), handling the unique challenges of live content delivery such as low-latency requirements, reliability, and the real-time nature of live streams compared to on-demand content.
Netflix's Ranker service had a video serendipity scoring feature (computing how different a title is from a user's watch history) consuming ~7.5% of total CPU per node, creating a significant performance bottleneck at their enormous scale.