Dependency graph
A dependency graph is a graph whose nodes represent entities and whose edges represent dependency relationships among them.
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 →
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.
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.
Related concepts
- dependency injectionaddressed by · Dependency injection is a software design technique in which a component receives its dependencies from outside rather than creating or locating them internally.
- structured extractionused by · Structured extraction is the process of identifying specified information in source content and representing it as organized data in a defined structure.
- dependencyuses · A software dependency is a component, resource, or prerequisite on which another software component or operation relies to function or proceed.
- waterfall visualizationcontrasts with · A waterfall visualization is a time-aligned display showing the sequence, duration, nesting, and overlap of activities or service executions.
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.