article thumbnail

Rapid Event Notification System at Netflix

The Netflix TechBlog

To this end, we developed a Rapid Event Notification System (RENO) to support use cases that require server initiated communication with devices in a scalable and extensible manner. In this blog post, we will give an overview of the Rapid Event Notification System at Netflix and share some of the learnings we gained along the way.

Systems 334
article thumbnail

DevOps automation: From event-driven automation to answer-driven automation [with causal AI]

Dynatrace

They need event-driven automation that not only responds to events and triggers but also analyzes and interprets the context to deliver precise and proactive actions. These initial automation endeavors paved the way for greater advancements, leading to the next evolution of event-driven automation.

DevOps 228
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Timestone: Netflix’s High-Throughput, Low-Latency Priority Queueing System with Built-in Support…

The Netflix TechBlog

Timestone: Netflix’s High-Throughput, Low-Latency Priority Queueing System with Built-in Support for Non-Parallelizable Workloads by Kostas Christidis Introduction Timestone is a high-throughput, low-latency priority queueing system we built in-house to support the needs of Cosmos , our media encoding platform. Over the past 2.5

Latency 212
article thumbnail

Consistent caching mechanism in Titus Gateway

The Netflix TechBlog

In that scenario, the system would need to deal with the data propagation latency directly, for example, by use of timeouts or client-originated update tracking mechanisms. We started seeing increased response latencies and leader servers running at dangerously high utilization. Let’s assume a sequence of events E?…E??,

Cache 224
article thumbnail

Migrating Netflix to GraphQL Safely

The Netflix TechBlog

Before GraphQL: Monolithic Falcor API implemented and maintained by the API Team Before moving to GraphQL, our API layer consisted of a monolithic server built with Falcor. A single API team maintained both the Java implementation of the Falcor framework and the API Server. To launch Phase 1 safely, we used AB Testing.

Traffic 353
article thumbnail

Migrating Critical Traffic At Scale with No Downtime?—?Part 1

The Netflix TechBlog

It provides a good read on the availability and latency ranges under different production conditions. These include options where replay traffic generation is orchestrated on the device, on the server, and via a dedicated service. Also, since this logic resides on the server side, we can iterate on any required changes faster.

Traffic 339
article thumbnail

Dynatrace supports the newly released AWS Lambda Response Streaming

Dynatrace

Customers can use AWS Lambda Response Streaming to improve performance for latency-sensitive applications and return larger payload sizes. The difference is the owner of the Lambda function does not have to worry about provisioning and managing servers. To learn more about the AWS Lambda features, visit the Lamba features page.

Lambda 224