liveBook · Manning

Directed acyclic graph

As explained in Delivering Machine Learning Projects: From design to deployment

A directed acyclic graph is a directed network of nodes and edges with no directed cycle.

A directed acyclic graph (DAG) represents a data pipeline as tasks connected by one-way dependencies, with no cycle. A workflow engine invokes the tasks in sequence without requiring a loop. section 4.3.3

In an ELT workflow, separate tasks can load tables from different systems, join them, and remove null values. Each task may contain internal steps or invoke another workflow, while the pipeline engine abstracts execution and management across technical stacks. section 4.3.3

Figure 4.1 An example DAG: it’s directed (D) as the information flows one way along the arrows. It’s acyclic (A) because there aren’t any cycles, and it’s a graph (G) because that’s what this sort of thing is called.

Use the DAG figure to distinguish directed information flow, acyclicity, and the graph structure. section 4.3.3

How Delivering Machine Learning Projects: From design to deployment covers it

How deep it goes
Defines direction and absence of cycles, then demonstrates loading, joining, and cleaning tasks without detailing graph algorithms.
Examples
Uses an ELT flow that loads two tables, joins them, and removes null values.
What you can do after
Operate and configure data pipelines through workflow engines that execute ordered transformation tasks.
How it connects
Connects data pipelines, workflow engines, schedulers, ELT, Hadoop, Oozie, and Apache Airflow.

Also explained in

Compare how 15 books explain directed acyclic graph →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Delivering Machine Learning Projects: From design to deployment. The section links point to the parts of the book it draws on.