Brendan Gregg

AUGUST 8, 2017

Linux load averages are "system load averages" that show the running thread (task) demand on the system as an average number of running plus waiting threads. I'll discuss these in the "Better Metrics" section near the end. ## History The original load averages show only CPU demand: the number of processes running plus those waiting to run.

Latency 111

Latency Metrics C++ Systems 111

The Netflix TechBlog

FEBRUARY 9, 2021

Plus, the architecture of the Edge tier was evolving to a PaaS (platform as a service) model, and we had some tough decisions to make about how, and where, to handle identity token handling. Team members presented this work at QCon San Francisco (and were two of the top three attended talks at the conference!):

Architecture 221

Architecture Latency Servers Website 221

InfoQ

OCTOBER 26, 2023

Aditi Gupta discusses the design choices made early on during service development that were crucial to scaling operations later on at Netflix. By Aditi Gupta

Design 55

Design Development Scalability Architecture 55

InfoQ

JULY 14, 2023

Mei-Chin Tsai, Vinod discuss the internal architecture of Azure Cosmos DB and how it achieves high availability, low latency, and scalability. By Mei-Chin Tsai, Vinod Sridharan

Latency 52

Latency Azure Availability Scalability 52

InfoQ

JULY 7, 2023

Facundo Agriel dives into the architecture of Magic Pocket, some early key design patterns, and the challenges of operating such a system at this scale. By Facundo Agriel

Systems 52

Systems Storage Architecture Design 52

InfoQ

JUNE 23, 2023

Frank Yu discusses how to decrease bandwidth usage and buffering across the system, protect against thundering herd problems, and simplify the logic of gateway and persistence services. By Frank Yu

Systems 52

Systems Design Scalability Architecture 52

InfoQ

FEBRUARY 17, 2023

Phil Calçado explores how they dealt with the hyper growth phase and what are the changes and initiatives they have put in place to make sure that they keep growing and pushing the envelope. By Phil Calçado

Design 52

Design Scalability Architecture Performance 52