The Netflix TechBlog
AUGUST 10, 2020
we announced our intention to stream video over 13 years ago, in January 2007?—?and Performance results In this section, we present an overview of the performance of our new encodes compared to our existing H.264 and have only increased both our device and content reach since then. Yet, given its wide support, our H.264/AVC
Rigor
SEPTEMBER 11, 2019
Reading time 16 min Whether you’re a web performance expert, an evangelist for the culture of performance, a web engineer incorporating performance into your process, or someone new to the web performance entirely, you probably identify as curious, excited about new ideas, and always learning. Rick Byers.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Percona
APRIL 12, 2023
MongoDB started out in 2007 as 10gen, a New York-based company looking to create a Platform as a Service (PaaS) solution. We are really pleased with our Q1 performance and see it as continued validation of the massive market we are pursuing, our strong product market fit, and our ability to execute.”
Dynatrace
JULY 24, 2023
The evolution of DevOps automation Since the concept of DevOps emerged around 2007 and 2008 in response to pain points with Agile development, DevOps automation has been continuously evolving. For instance, in the case of poor performance, you can seamlessly toggle a feature flag and mitigate any detrimental effects.
The Netflix TechBlog
FEBRUARY 13, 2023
Our goal in building a media-focused ML infrastructure is to reduce the time from ideation to productization for our media ML practitioners. Even after gaining access, one needed to deal with the challenges of homogeneity across different assets in terms of decoding performance, size, metadata, and general formatting.
The Netflix TechBlog
JANUARY 10, 2024
The Netflix video processing pipeline went live with the launch of our streaming service in 2007. Finally, relevant abstractions allow media algorithm developers to focus on the manipulation of video and audio signals rather than on infrastructural concerns. Over the years, the system expanded to support various new use cases.
The Netflix TechBlog
MARCH 1, 2021
The first generation of this system went live with the streaming launch in 2007. Dealing with production issues became an expensive chore that placed a tax on all developers because infrastructure code was all mixed up with application code. The second generation added scale but was extremely difficult to operate.
Expert insights. Personalized for you.
239 
Let's personalize your content