Marius Eriksen's guest appearances

Marius Eriksen

Machine Learning Archives - Software Engineering Daily

Software Daily

Zach Allen

Jeff Johnson

Simon Chan

Dario Amodei

Lukas Biewald

Kelley Rivoire

Mike Tung

Alexandr Wang

Tim Williamson

Andrew Mason

George Hotz

Xin Wang

Mike Lee

Adam Gibson

Charlie Gerard

OwlTail

The volume of data in the world is always increasing. The costs of storing that data is always decreasing. And the means for processing that data is always evolving. Sensors, cameras, and other small computers gather large quantities of data from the physical world around us. User analytics tools gather information about how we are interacting with the Internet. Logging servers collect terabytes of records about how our systems are performing. From the popularity of MapReduce, to the rise of open source distributed processing frameworks like Spark and Flink, to the wide variety of cloud services like BigQuery: there is an endless set of choices for how to analyze gigantic sets of data.  Machine learning training and inference is another dimension of the modern data engineering stack. Whereas tools like Spark and BigQuery are great for performing ad-hoc queries, systems like TensorFlow are optimized for the model training and deployment process. Stitching together these tools allows a developer to compose workflows for how data pipelines progress through a data engineering system. One popular tool for this is Apache Airflow, which was created in 2014 and is widely used at companies like Airbnb. Over the next few years, we will see a proliferation of new tools in the world of data engineering–and for good reason. There is a wealth of opportunity for companies to leverage their data to make better decisions, and potentially to clean and offer their internal data as APIs and pre-trained machine learning models. Today, there is a vast number of enterprises who are modernizing their software development process with Kubernetes, cloud providers, and continuous delivery. Eventually, these enterprises will improve their complex software architecture, and will move from a defensive position to an offensive one. These enterprises will shift their modernization efforts from “DevOps” to “DataOps”, and thousands of software vendors will be ready to sell them new software for modernizing their data platform. There is not a consensus for the best way to build and run a “data platform”. Nearly every company we have talked to on the show has a different definition and a different architecture for their “data platform”: Doordash, Dremio, Prisma, Uber, MapR, Snowflake, Confluent, Databricks… We don’t expect to have a concise answer for how to run a data platform any time soon–but on the bright side, data infrastructure seems to be improving. Companies are increasingly able to ask questions about their data and get quick answers, in contrast to the data breadlines that were so prevalent five years ago.  Today we cover yet another approach to large scale data processing. Reflow is a system for incremental data processing in the cloud. Reflow includes a functional, domain specific language for writing workflow programs, a runtime for evaluating those programs incrementally, and a scheduler for dynamically provisioning resources for those workflows. Reflow was created for large bioinformatics workloads, but should be broadly applicable to scientific and engineering computing workloads. Reflow  evaluates programs incrementally. Whenever the input data or the program changes, only the outputs that depend on the changes are recomputed. This minimizes the amount of recomputation that needs to be performed across a computational graph. Marius Eriksen is the creator of Reflow and an engineer at GRAIL. He joins the show to discuss the motivation for a new data processing system–which involves explaining why workloads in bioinformatics are different than in some other domains. The post Reflow: Distributed Incremental Processing with Marius Eriksen appeared first on Software Engineering Daily.

The volume of data in the world is always increasing. The costs of storing that data is always decreasing. And the means for processing that data is always evolving. Sensors, cameras, and other small computers gather large quantities of data from the physical world around us. User analytics tools gather information about how we are interacting with the Internet. Logging servers collect terabytes of records about how our systems are performing. From the popularity of MapReduce, to the rise of open source distributed processing frameworks like Spark and Flink, to the wide variety of cloud services like BigQuery: there is an endless set of choices for how to analyze gigantic sets of data. Machine learning training and inference is another dimension of the modern data engineering stack. Whereas tools like Spark and BigQuery are great for performing ad-hoc queries, systems like TensorFlow are optimized for the model training and deployment process. Stitching together these tools allows a developer to compose workflows for how data pipelines progress through a data engineering system. One popular tool for this is Apache Airflow, which was created in 2014 and is widely used at companies like Airbnb. Over the next few years, we will see a proliferation of new tools in the world of data engineering–and for good reason. There is a wealth of opportunity for companies to leverage their data to make better decisions, and potentially to clean and offer their internal data as APIs and pre-trained machine learning models. Today, there is a vast number of enterprises who are modernizing their software development process with Kubernetes, cloud providers, and continuous delivery. Eventually, these enterprises will improve their complex software architecture, and will move from a defensive position to an offensive one. These enterprises will shift their modernization efforts from “DevOps” to “<a href="https://softwareengineeringdaily.com/2018/10/18/dataops-and-the-data-platform/" rel="nofollow" target="_blank">DataOps</a>”, and thousands of software vendors will be ready to sell them new software for modernizing their data platform. There is not a consensus for the best way to build and run a “data platform”. Nearly every company we have talked to on the show has a different definition and a different architecture for their “data platform”: <a href="https://softwareengineeringdaily.com/2018/08/16/doordash-engineering-with-raghav-ramesh/" rel="nofollow" target="_blank">Doordash</a>, <a href="https://softwareengineeringdaily.com/2018/06/18/dremio-data-engineering-with-tomer-shiran/" rel="nofollow" target="_blank">Dremio</a>, <a href="https://softwareengineeringdaily.com/2018/09/28/prisma-graphql-infrastructure-with-soren-bramer-schmidt/" rel="nofollow" target="_blank">Prisma</a>, <a href="https://softwareengineeringdaily.com/2018/05/24/ubers-data-platform-with-zhenxiao-luo/" rel="nofollow" target="_blank">Uber</a>, <a href="https://softwareengineeringdaily.com/tag/mapr/" rel="nofollow" target="_blank">MapR</a>, <a href="https://softwareengineeringdaily.com/2018/10/15/data-warehouse-with-christian-kleinerman/" rel="nofollow" target="_blank">Snowflake</a>, <a href="https://softwareengineeringdaily.com/2017/07/10/kafka-in-the-cloud-with-neha-narkhede/" rel="nofollow" target="_blank">Confluent</a>, <a href="https://softwareengineeringdaily.com/2018/02/26/spark-and-streaming-with-matei-zaharia/" rel="nofollow" target="_blank">Databricks</a>… We don’t expect to have a concise answer for how to run a data platform any time soon–but on the bright side, data infrastructure seems to be improving. Companies are increasingly able to ask questions about their data and get quick answers, in contrast to the data breadlines that were so prevalent five years ago. Today we cover yet another approach to large scale data processing. <a href="https://github.com/grailbio/reflow" rel="nofollow" target="_blank">Reflow</a> is a system for incremental data processing in the cloud. Reflow includes a functional, domain specific language for writing workflow programs, a runtime for evaluating those programs incrementally, and a scheduler for dynamically provisioning resources for those workflows. Reflow was created for large bioinformatics workloads, but should be broadly applicable to scientific and engineering computing workloads. Reflow  evaluates programs incrementally. Whenever the input data or the program changes, only the outputs that depend on the changes are recomputed. This minimizes the amount of recomputation that needs to be performed across a computational graph. Marius Eriksen is the creator of Reflow and an engineer at GRAIL. He joins the show to discuss the motivation for a new data processing system–which involves explaining why workloads in bioinformatics are different than in some other domains. The post <a href="https://softwareengineeringdaily.com/2018/11/16/reflow-distributed-incremental-processing-with-marius-eriksen/" rel="nofollow" target="_blank">Reflow: Distributed Incremental Processing with Marius Eriksen</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Reflow: Distributed Incremental Processing with Marius Eriksen