Speaker
Abstract
Incremental processing, an approach that processes only new or updated data in workflows, substantially reduces compute resource costs and execution time, leading to fewer potential failures and less need for manual intervention. However, enabling incremental processing on large-scale data pipelines and workflows presents significant challenges around scalability, ease of adoption, and user experience. In this talk, we will discuss how we are leveraging Apache Iceberg and Netflix Maestro to build an Incremental Processing Solution (IPS) that enables incremental processing of only new or changed data, reducing compute costs and processing times while ensuring data accuracy and freshness. By combining Iceberg's metadata capabilities for snapshots and data files with Maestro's workflow orchestration, we can efficiently handle late-arriving data and backfills in various different scenarios beyond append-only mode.
We will share our experiences and insights into how this IPS has empowered our data engineering teams to build more reliable, efficient, and scalable data pipelines, unlocking new data processing patterns. Through real-world use cases, we will demonstrate how IPS has significantly improved resource utilization, reduced execution times, and simplified pipeline management, all while maintaining data integrity. Additionally, we will discuss the emerging incremental processing patterns that we have discovered, such as using captured change data for row-level filtering and leveraging range parameters in business logic, as well as the techniques, best practices, and lessons learned from our journey towards incremental processing at Netflix.
Interview
I am the tech lead of the Big Data Orchestration team at Netflix. Our team builds multiple workflow and job orchestration services, such as Maestro. My work focuses on designing and building the Netflix workflow orchestrator, a robust and scalable platform that provides workflow as a service. It is widely used by thousands of Netflix internal users. With Netflix's scale, one of my primary responsibilities is to develop Maestro to support a wide variety of use cases while being able to scale up and out to automate hundreds of thousands of data and ML pipelines. Additionally, I work on integrating Maestro with other systems to offer new features for data practitioners and meet evolving business needs, such as efficient incremental processing support. More recently, I have been exploring how to expand workflow orchestration into the AI domain, for example, by supporting AI agentic workflows.
Over the years, we have learned that incremental processing significantly improves resource utilization, reduces execution times, and simplifies pipeline management, all while maintaining data integrity. We have also identified several emerging incremental processing patterns, such as using captured change data for row-level filtering and leveraging range parameters in business logic. We want to share these insights, along with the techniques, best practices, and lessons learned from our journey towards incremental processing at Netflix.
The audience is expected to have basic understandings of data processing, data pipelines, and open table formats (e.g., Iceberg).
Someone will walk away with an understanding of how the Incremental Processing System (IPS) works and how it can empower data practitioners to build more reliable, efficient, and scalable data pipelines using new data processing patterns.
I believe AI agent orchestration will be the next big disruption in the orchestration area.
Topics
QCon San Francisco 2024 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.
From the same track
Tuesday 19 November
10:35 Ballroom A Session Platform Engineering Beyond Durability: Enhancing Database Resilience and Reducing the Entropy Using Write-Ahead Logging at Netflix Prudhviraj Karumanchi, Vidhya Arvind In modern database systems, durability guarantees are crucial but often insufficient in scenarios involving extended system outages or data corruption. 11:45 Pacific DEKJ Session Architecture OpenSearch Cluster Topologies for Cost-Saving Autoscaling Amitai Stern Engineering Manager @Logz.io, Managing Observability Data Storage of Petabyte Scale, OpenSearch Leadership Committee Member and Contributor The indexing rates of many clusters follow some sort of fluctuating pattern - be it day/night, weekday/weekend, or any sort of duality when the cluster changes from being active to less active. In these cases how does one scale the cluster? 13:35 Ballroom A Session Stream All the Things — Patterns of Effective Data Stream Processing Adi Polak Director, Advocacy and Developer Experience Engineering @Confluent, Author of "Scaling Machine Learning with Spark" and "High Performance Spark 2nd Edition" Data streaming is a really difficult problem. Despite 10+ years of attempting to simplify it, teams building real-time data pipelines can spend up to 80% of their time optimizing it or fixing downstream output by handling bad data at the lake. 14:45 Ballroom A Session Stream and Batch Processing Convergence in Apache Flink Jiangjie (Becket) Qin Principal Staff Software Engineer @LinkedIn, Data Infra Engineer, PMC Member of Apache Kafka & Apache Flink, Previously @Alibaba and @IBM The idea of executing streaming and batch jobs with one engine has been there for a while. People always say batch is a special case of streaming. Conceptually, it is. 15:55 Ballroom A Session Data Pipelines Efficient Incremental Processing with Netflix Maestro and Apache Iceberg Jun He Staff Software Engineer @Netflix, Managing and Automating Large-Scale Data/ML Workflows, Previously @Airbnb and @Hulu Incremental processing, an approach that processes only new or updated data in workflows, substantially reduces compute resource costs and execution time, leading to fewer potential failures and less need for manual intervention. 17:05 Seacliff D Unconference Unconference: Shift-Left Data Architecture