Skip to content

Dependency

A dependency is software, infrastructure, or an external service that another part of a website relies on to function.

A dependency is software, a service, library, platform, or system that another part of the website relies on to function.

Dependencies allow teams to build on existing tools instead of recreating everything themselves.

Common Website Dependencies

Dependencies can include:

A modern website usually has many dependencies.

That is normal.

Dependency vs. Integration

An Integration describes a connection between systems.

A dependency describes something the website relies on.

An integrated service often becomes a dependency, but not every dependency represents a system integration.

For example:

CSS framework → dependency

but not necessarily:

external integration.

Dependency Cost

Every dependency introduces some combination of:

  • Maintenance
  • Updates
  • Compatibility requirements
  • Performance cost
  • Vendor reliance
  • Security considerations
  • Documentation
  • Billing
  • Failure risk

That does not mean dependencies should be avoided.

It means they should provide enough value to justify their cost.

Dependencies and Plugin Bloat

Plugin Bloat is one CMS-specific example of unmanaged dependency growth.

But dependency problems can occur even without plugins.

A site might rely on:

  • Five external scripts
  • Three APIs
  • Two automation platforms
  • One legacy database

while appearing technically simple inside the CMS.

Common Problems

Common problems include:

  • Dependency no longer maintained
  • Nobody knows why it exists
  • Several tools perform the same job
  • Version cannot be upgraded
  • Service subscription expires
  • External API changes
  • Dependency injected globally despite being needed once
  • Critical service controlled through contractor account

How to Improve

Maintain an inventory of important dependencies.

For each one, understand:

  • Purpose
  • Owner
  • Version
  • Vendor
  • Cost
  • Update process
  • Failure behaviour
  • Replacement difficulty

Review dependencies during maintenance rather than only after something breaks.