liveBook · Manning

Dependency graph

A dependency graph is a graph whose nodes represent entities and whose edges represent dependency relationships among them.

How 9 Manning books explain it

Vibe Engineering

A dependency map is a structured record of which software services depend on or communicate with one another.

How it is used
Guides agents to the right projects and identifies consumers potentially affected by changes.
How deep it goes
Explains forward and reverse queries and an affected-test workflow, while noting the coordination cost of strict dependency enforcement.
Examples
Uses Bazel queries against checkout and shared-utils, plus a serialization-library upgrade across consuming services.
What you can do after
Apply it via Bazel queries to locate dependencies, identify affected consumers, and select tests before submitting a change.

Read how Vibe Engineering explains dependency graph →

ASP.NET Core in Action, 3e

A dependency graph is a directed graph representing objects or components and the dependencies required to construct or operate them.

How it is used
Uses the graph to explain why dependency injection removes manual object construction from minimal API handlers.
How deep it goes
Defines the graph and works through nested email-service construction, but defers service lifetimes to later treatment.
Examples
Uses RegisterUser, EmailSender, MessageFactory, NetworkClient, EmailServerSettings, and LinkGenerator to demonstrate graph construction and resolution.
What you can do after
Understand how the DI container constructs requested services from their declared dependencies and supplies them to handlers.

Read how ASP.NET Core in Action, 3e explains dependency graph →

Fast by Default

A dependency graph is a graph that represents operations as nodes and their execution dependencies as directed edges.

How it is used
Maps request dependencies to identify artificial waterfalls and reduce the operations users must wait for.
How deep it goes
Explains nodes, dependency arrows, parallel branches, and critical paths, then stops short of formal graph algorithms.
Examples
Uses a team dashboard, independent user-data requests, profile-dependent team metrics, network waterfalls, and optimized request graphs.
What you can do after
Diagnose/debug with it by locating unnecessary sequential hops and restructuring independent requests for parallel execution.

Read how Fast by Default explains dependency graph →

Cloud Observability in Action

A service map is a graphical representation of the services in a distributed system and their communication relationships.

How it is used
Maps actual service communication in distributed systems and provides an architectural starting point for observability and troubleshooting.
How deep it goes
Explains graph purpose and limitations, then defers temporal behavior to traces, spans, and waterfall visualizations.
Examples
Uses an e-commerce checkout path and a Jaeger happy-path dependency graph to illustrate service relationships and investigation.
What you can do after
Diagnose/debug with Jaeger by inspecting a dependency graph, selecting a trace, and switching to spans for timing details.

Read how Cloud Observability in Action explains dependency graph →

Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

A dependency graph represents infrastructure resources and the dependency relationships among them.

How it is used
Guides brownfield infrastructure migration and structures IaC changes in dependency order.
How deep it goes
Defines the graph and supplies an ordered migration procedure across foundational, compute, orchestration, and application resources.
Examples
Uses networks, servers, databases, queues, DNS, SSL certificates, and Kubernetes deployments as migration examples.
What you can do after
Apply it via Terraform by assessing dependencies and sequencing resource migration from foundational infrastructure upward.

Read how Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform explains dependency graph →

Natural Language Processing in Action, Second Edition

A dependency tree is a tree representation of grammatical relationships in which words depend on other words within a sentence.

How it is used
Uses grammatical relationships to inspect sentence structure and extract facts for knowledge graphs.
How deep it goes
Explains roots, dependents, branching, and visualization, but does not detail the parsing algorithm itself.
Examples
Demonstrates spaCy and displaCy on a sentence about survival, including a rendered SVG dependency diagram.
What you can do after
Operate spaCy and displaCy to render dependency diagrams and inspect grammatical relationships in processed text.

Read how Natural Language Processing in Action, Second Edition explains dependency graph →

Quarkus in Action

A bean dependency graph is a visual graph representing dependency relationships among managed beans.

How it is used
Uses Quarkus Dev UI to inspect dependency relationships among application beans.
How deep it goes
Defines and visualizes bean dependencies, but does not explain dependency resolution internals.
Examples
Shows the dependency graph for the GreetingResource REST endpoint.
What you can do after
Evaluate bean dependencies through a visual graph in Quarkus Dev UI.

Read how Quarkus in Action explains dependency graph →

Testing Spring Boot Applications

A dependency graph is a graph representing components and the dependency relationships among them.

How it is used
Uses dependency relationships to define focused Spring Boot test contexts and decide whether to expand scope or provide substitute beans.
How deep it goes
Explains graph scope, multilevel dependency discovery, bean leaves, and stub substitution, but does not formalize graph algorithms.
Examples
Uses ThingConfiguration, GreenThing, YellowGizmo, BlueWidget, selected classes, and repository leaves as concrete graph examples.
What you can do after
Configure focused Spring Boot tests by identifying missing dependencies, supplying stubs, and selecting suitable data slices.

Read how Testing Spring Boot Applications explains dependency graph →

Secrets of the JavaScript Ninja, Third Edition

A graph representing dependencies among components of a software project.

How it is used
Makes dependencies explicit so build tools can infer code order and manage loading.
How deep it goes
Explains build-time benefits and tree-shaking, but does not detail graph construction.
Examples
Contrasts serial script tags and global-variable dependencies with explicit module dependencies.
What you can do after
Understand how explicit dependencies support inferred ordering, build-time error detection, and unused-code pruning.

Read how Secrets of the JavaScript Ninja, Third Edition explains dependency graph →

Also covered in

What to know first

Related concepts

Questions about dependency graph

What is dependency graph?

A dependency graph is a graph whose nodes represent entities and whose edges represent dependency relationships among them.

Which Manning books explain dependency graph?

Vibe Engineering, ASP.NET Core in Action, 3e, Fast by Default, Cloud Observability in Action, Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform, Natural Language Processing in Action, Second Edition, Quarkus in Action, Testing Spring Boot Applications and 1 more.

What should I know before learning dependency graph?

Manning books that teach dependency graph usually introduce dependency, contract, language model and pipeline first.

What is dependency graph a kind of?

Dependency graph is a kind of graph. A graph is a mathematical structure consisting of vertices and edges that connect pairs of vertices to represent relationships or connections.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.