Track host
About the track
In the rapidly evolving digital landscape, the way we approach data architecture is undergoing a transformative shift. This shift is not just about adopting new technologies but about fundamentally rethinking our approach to data management, governance and architecture design. Welcome to the concept of "Shift-Left Data Architecture" – a methodology that promises to set the foundation for future-ready data ecosystems.
As data's role in decision-making, operations and machine learning has become increasingly critical, the need for a more proactive approach has become evident. We need to reconsider traditional methods where data considerations, and supporting ML often came later in the development process, which led to inefficiencies, increased costs, and data quality and outcomes issues. By shifting left, organizations can avoid costly revisions, enhance data security, and ensure that their data architecture is robust and scalable.
Join us to learn more about this new era in data architectures, the building blocks of a shift-left architecture, the tools and technologies that enable it, and gain insights on how to implement these principles effectively within your organization.
Sessions in this track
Tuesday 19 November. 6 sessions per track, chosen and introduced by the Track Host.
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 ArchitectureQCon 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.