Rate this page:
A component dependency is a relationship between two components, where one component relies on another for functionality or availability.
A distributed architecture has a collection of components that depend on one another. As you add more components to your architecture, the number of dependencies increases, leading to a complex orchestration of components. When components depend on one another, several factors such as downtime, deployment, security issues, and status of a component affect its dependent components. In a complex architecture, it is difficult to identify the impacts.
Mapping component dependencies enables you to identify the things that impact a component or those that a component impacts. It helps you to:
You can add a component dependency from the Dependencies section on the component’s details page.
Currently, Compass supports the Depends on dependency type. Learn more about the available component dependency types
To add a dependency to a component:
The component's dependency is recorded in Compass.
You can remove the record of a component’s dependency on another component from the Dependencies section on the component’s details page.
To remove a dependency from a component:
The component dependency is no longer recorded in Compass.
Your Compass site comes with the following dependency type:
Describes the relationship of a component on another component that is necessary for it to operate.
For example, you could describe that an component a component as part of its build.
Any type of component can depend on any other type of component in Compass.
Rate this page: