Netflix的Cosmos平台是下一代媒体计算平台，旨在通过提高灵活性、效率和开发人员的生产力，现代化Netflix的媒体处理流程。其中一个微服务是视频编码服务（VES），它将输入的原始素材编码成适合Netflix流媒体或某些工作室/制作用途的视频流。VES通过多个编解码器格式、分辨率和质量级别的支持，满足多设备、低延迟、快速创新和成本效益的要求。VES构建在Cosmos的三个层级上，包括API层（Optimus）、工作流层（Plato）和无服务器计算层（Stratum），并通过优先级消息传递系统Timestone进行异步通信。VES的构建过程中，团队学到了微服务架构的多个经验教训，包括定义适当的服务范围和通过持续发布来支持新的业务需求、提升性能和改进韧性。在第二次迭代中，团队通过将不同编解码器格式的编码合并到一个服务中，减少了代码重复，同时保证了每种编解码器格式的独立演进。此外，团队还强调了在数据建模方面要实事求是，平衡共享和耦合的关系。

Netflix的Content Engineering团队与Studio Engineering团队合作开发了Reverse Search功能。该功能可以根据文档查询与之匹配的搜索条件，实现精确的查询结果。通过将搜索条件保存为SavedSearches，并将其转换为Elasticsearch查询语句，在percolator字段中进行索引。此外，reverse search还可用于创建更响应的UI。通过GraphQL订阅，搜索结果可以实时更新，而不是一次性查询。这些订阅可以与SavedSearch相关联，并利用reverse search来确定何时更新订阅返回的键集合。总之，reverse search是一个功能强大的外部标准匹配器，不仅适用于电影标准，还可用于任何具有逆向搜索能力的索引。

Netflix开发了Auto Remediation功能，旨在自动修复失败的作业。该功能通过规则分类器和机器学习服务集成，可以处理由错误配置引起的错误，并分类新错误。Auto Remediation使用规则分类器进行初始分类，然后使用机器学习服务生成推荐配置。推荐配置存储于配置服务中，并自动应用。通过与Spark作业故障的生产部署验证了Auto Remediation的有效性和潜力。其优化器通过探索Spark配置参数空间来推荐最小化重试失败概率和成本的配置。预测模型每天离线重新训练，并在每个候选配置参数值上调用优化器进行评估。如果优化器找到可行的配置解决方案，响应中包含此推荐配置，由ConfigService用于更改重试的配置。如果没有可行的解决方案，响应中包含禁用重试的标记，从而消除了计算成本的浪费。训练时，使用了Feedforward Multilayer Perceptron (MLP)模型，将任务的元数据特征进行处理，并使用特征哈希和嵌入层进行建模。模型经过验证后存储在Metaflow Hosting中，然后由优化器根据每个配置请求进行调用。

In this post, we’re excited to introduce SafeTest, a revolutionary library that offers a fresh perspective on End-To-End (E2E) tests for web-based User Interface (UI) applications.

Can you spot any difference between the two data streams below? Each observation is the time interval between a Netflix member hitting the play button and playback commencing, i.e., play-delay. These observations are from a particular type of A/B test that Netflix runs called a software canary or regression-driven experiment. More on that below — for now, what’s important is that we want to quickly and confidently identify any difference in the distribution of play-delay — or conclude that, within some tolerance, there is no difference.

In this blog post, we will develop a statistical procedure to do just that, and describe the impact of these developments at Netflix. The key idea is to switch from a “fixed time horizon” to an “any-time valid” framing of the problem.

This is the first blog in a multi-part series on how Netflix rebuilt its video processing pipeline with microservices, so we can maintain our rapid pace of innovation and continuously improve the system for member streaming and studio operations. This introductory blog focuses on an overview of our journey. Future blogs will provide deeper dives into each service, sharing insights and lessons learned from this process.

A framework to identify the causal impact of successful visual components.

本文介绍了Netflix在处理延迟到达数据时采用的增量处理模式。作者详细解释了增量处理模式的应用场景和用例，并提供了一个使用增量处理重新构建的数据流程示例。通过使用增量处理模式，Netflix成功降低了计算成本和执行时间。文章还提到了一些对业务逻辑的更改，如将playback_daily_table与playback_daily_icdc_table进行JOIN，以处理延迟到达的数据。通过这些改变，数据管道的效率得到了极大提升，新的基于IPS的管道只需要原来的资源的约10%的时间来完成。作者还展望了IPS的未来发展，并感谢参与开发IPS的同事们的建议和反馈。

Netflix的Membership and Finance Data Engineering团队负责处理与计划、定价、会员生命周期和收入相关的多样化数据，以支持分析、驱动各种仪表盘，并做出数据驱动的决策。然而，当数据延迟到达时，管理数据可能会带来很大的挑战。为了解决这个问题，团队开发了一个增量数据处理框架Psyberg。这个框架可以处理延迟到达的数据，并确保数据的准确性和完整性。通过这个系列的博客文章，读者可以了解Psyberg框架的内部机制、独特特性以及如何与数据流水线集成。Psyberg框架的使用使得数据处理更加高效、准确和及时。

Psyberg是一个数据处理平台，支持无状态和有状态的数据处理模式。对于无状态模式，它根据提供的输入检测Iceberg快照的变化，并将相关信息存储在psyberg_session_f表中。对于有状态模式，它可以处理多个输入流，并根据不同的时间戳字段来跟踪源表快照的变化。无论是哪种模式，Psyberg都能解析出每个Iceberg快照的分区信息。

本文介绍了Psyberg如何帮助自动化处理数据管道的端到端补偿，包括维度表。文章首先介绍了Psyberg的核心操作模式，即无状态和有状态数据处理。然后，介绍了在集成Psyberg后管道的状态。文章详细解释了Psyberg如何处理延迟到达的数据，并提供了一个通用的处理流程。最后，强调了Psyberg的优点和适用性。文章总结了如何将Psyberg与客户生命周期的四个组件集成，实现自动补偿。

When you enjoy the latest season of Stranger Things or Casa de Papel (Money Heist), have you ever wondered about the secrets to fantastic story-telling, besides the stunning visual presentation? From the violin melody accompanying a pivotal scene to the soaring orchestral arrangement and thunderous sound-effects propelling an edge-of-your-seat action sequence, the various components of the audio soundtrack combine to evoke the very essence of story-telling. To uncover the magic of audio soundtracks and further improve the sonic experience, we need a way to systematically examine the interaction of these components, typically categorized as dialogue, music and effects.

In this blog post, we will introduce speech and music detection as an enabling technology for a variety of audio applications in Film & TV, as well as introduce our speech and music activity detection (SMAD) system which we recently published as a journal article in EURASIP Journal on Audio, Speech, and Music Processing.

At Netflix, we strive to give our members an excellent personalized experience, helping them make the most successful and satisfying selections from our thousands of titles. We already personalize artwork and trailers, but we hadn’t yet personalized sizzle reels — until now.

A sizzle reel is a montage of video clips from different titles strung together into a seamless A/V asset that gets members excited about upcoming launches (for example, our Emmys nominations or holiday collections). Now Netflix can create a personalized sizzle reel dynamically in real time and on demand. The order of the clips and included titles are personalized per member, giving each a unique and effective experience. These new personalized reels are called Dynamic Sizzles.

In this post, we will dive into the exciting details of how we create Dynamic Sizzles with minimal human intervention, including the challenges we faced and the solutions we developed.

Empowering video editors with multimodal machine learning to discover perfect moments across the entire Netflix catalog.

Data powers much of what we do at Netflix. On the Data Platform team, we build the infrastructure used across the company to process data at scale.

In our last blog post, we introduced “Data Mesh” — A Data Movement and Processing Platform. When a user wants to leverage Data Mesh to move and transform data, they start by creating a new Data Mesh pipeline. The pipeline is composed of individual “Processors” that are connected by Kafka topics. The Processors themselves are implemented as Flink jobs that use the DataStream API.

Since then, we have seen many use cases (including Netflix Graph Search) adopt Data Mesh for stream processing. We were able to onboard many of these use cases by offering some commonly used Processors out of the box, such as Projection, Filtering, Unioning, and Field Renaming.

Netflix’s service mesh adoption: history, motivations, and how we worked with the Envoy community on a feature to streamline mesh adoption.