Dependency management
Dependency management is the practice of identifying, declaring, resolving, coordinating, and maintaining the components or resources on which a software project depends.
Go in Practice, Second Edition
Dependency management is the process of declaring, resolving, obtaining, and maintaining software components required by an application.
- How it is used
- Supports application development by managing packages and local or external dependencies within the Go toolchain.
- How deep it goes
- Explains import names, grouping, package prefixes, and compile-time motivation, but does not detail dependency version resolution or maintenance.
- Examples
- Uses fmt.Println, grouped standard-library and external imports, and the `go get ./...` command.
- What you can do after
- Apply it via go mod and package imports to work with standard-library, local-module, and external packages.
Read how Go in Practice, Second Edition explains dependency management →
Spring in Action, Sixth Edition
Dependency management is the practice of declaring, resolving, and controlling the external libraries required by an application.
- How it is used
- Declares and controls application libraries in a Maven-based Spring Boot project.
- How deep it goes
- Explains parent-managed versions, declared dependencies, and starter transitivity without detailing conflict-resolution procedures.
- Examples
- Uses a generated pom.xml containing Web, Thymeleaf, DevTools, and testing dependencies.
- What you can do after
- Operate Maven dependency configuration by declaring starters and inheriting versions from Spring Boot’s parent POM.
Read how Spring in Action, Sixth Edition explains dependency management →
Simple Object-Oriented Design: Create clean, maintainable applications
Dependency management is the discipline of controlling relationships among software components so that changes remain localized and maintainability is preserved.
- How it is used
- Frames maintainability work around limiting coupling and preventing changes from rippling through object-oriented systems.
- How deep it goes
- Explains coupling, transitive change effects, information hiding, and practical questions for choosing stable abstractions.
- Examples
- Uses Basket, Product, Customer, DiscountRules, and DiscountRepository to illustrate direct and transitive change propagation.
- What you can do after
- Apply it to reduce unnecessary dependencies, conceal volatile details, and assess the change risk of class relationships.
Go in Action, Second Edition
Dependency management is the process of declaring, resolving, versioning, and obtaining software components required by a project.
- How it is used
- Organizes separately managed Go modules so shared definitions and implementations can support services without tight coupling.
- How deep it goes
- Explains module initialization, requirement updates, version selection, transitive dependencies, and checksum verification without detailing resolver internals.
- Examples
- Uses go mod init, go get, go mod tidy, go.mod requirements, and go.sum checksum entries.
- What you can do after
- Operate Go's module tooling to declare, fetch, update, verify, and reproduce project dependencies.
Read how Go in Action, Second Edition explains dependency management →
Code Like a Pro in Rust
Package and dependency management is the practice of declaring, resolving, retrieving, and maintaining software packages and their dependencies.
- How it is used
- Uses Cargo to declare and obtain third-party crates instead of manually integrating libraries and build systems.
- How deep it goes
- Explains registry rationale, Cargo.toml declarations, cargo add, and SemVer ranges, but does not detail lockfiles or resolution internals.
- Examples
- Demonstrates rand through Cargo.toml, cargo add, and a SemVer operator comparison table.
- What you can do after
- Operate/configure Cargo by declaring crates and selecting compatible dependency version ranges.
Read how Code Like a Pro in Rust explains dependency management →
Also covered in
- Grokking Web Application Security
- Think Like a Software Engineering Manager
- The Art of AI Product Development
- Data Pipelines with Apache Airflow, Second Edition
- Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more
- Google Anthos in Action
- Python How-To
- Systems Programming with ZigIn early access (MEAP)
- Spring Start Here, Second EditionIn early access (MEAP)
- Build an AI Agent (From Scratch)
- Java Persistence with Spring Data and Hibernate epub
What to know first
- dependencyA dependency is a component, resource, or prerequisite that another software component or activity relies on to function, build, or proceed.
- deployment pipelineA deployment pipeline is a repeatable sequence of stages that builds, tests or validates, packages, and delivers software changes toward release or deployment.
- web applicationA web application is software that provides functionality through web technologies and is accessed over a network, typically through a browser or other web client.
- containerA software container is an isolated execution environment that packages an application and its dependencies, typically sharing the host operating-system kernel.
Related concepts
- container imageaddressed by · A container image is a packaged filesystem and metadata artifact from which a container can be created and run.
- dependencyuses · A dependency is a component, resource, or prerequisite that another software component or activity relies on to function, build, or proceed.
- lock fileuses · A lock file records resolved dependency versions and related metadata so a package manager can reproduce a project's dependency installation.
Questions about dependency management
What is dependency management?
Dependency management is the practice of identifying, declaring, resolving, coordinating, and maintaining the components or resources on which a software project depends.
Which Manning books explain dependency management?
Go in Practice, Second Edition, Spring in Action, Sixth Edition, Simple Object-Oriented Design: Create clean, maintainable applications, Go in Action, Second Edition and Code Like a Pro in Rust.
What should I know before learning dependency management?
Manning books that teach dependency management usually introduce dependency, deployment pipeline, web application and container first.
What are the parts of dependency management?
Dependency management includes bill of materials.
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.




