The Netflix TechBlog

JANUARY 10, 2024

The Netflix video processing pipeline went live with the launch of our streaming service in 2007. This architecture shift greatly reduced the processing latency and increased system resiliency. Future blogs will provide deeper dives into each service, sharing insights and lessons learned from this process.

Processing 229

Processing Media Latency Innovation 229

The Netflix TechBlog

MARCH 1, 2021

It supports both high throughput services that consume hundreds of thousands of CPUs at a time, and latency-sensitive workloads where humans are waiting for the results of a computation. The first generation of this system went live with the streaming launch in 2007.

Serverless 228

Serverless Media Latency Social Media 228

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.

DevOps 209

DevOps Traffic Efficiency Servers 209

Alex Russell

APRIL 29, 2021

Classics of the genre include: Apple's just focused on performance! The Performance Argument. As an engineer on a browser team, I'm privy to the blow-by-blow of various performance projects, benchmark fire drills, and the ways performance marketing (deeply) impacts engineering priorities. Steve & Tim's Close-up Magic.

Media 145

Media Games Education Engineering 145

O'Reilly Software

MARCH 7, 2018

Although the ideas of reactive and streaming are nowhere near new, and keeping in mind that mere novelty doesn’t imply greatness, it is safe to say they have proven themselves and matured enough to see many programming languages, platforms, and infrastructure products embrace them fully. Most well-known is probably Apache Camel.

Transportation 72

Transportation Java Programming Architecture 72

All Things Distributed

OCTOBER 2, 2017

We were pushing the limits of what was a leading commercial database at the time and were unable to sustain the availability, scalability and performance needs that our growing Amazon business demanded. Performant – The service would need to be able to maintain consistent performance in the face of diverse customer workloads.

Internet 128

Internet Internet AWS Performance 128