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
If you manage your component via config-as-code, you must also use config-as-code to add dependencies. You won’t be able to do so from the dependencies list. Learn how to update your component managed via config-as-code
To add a dependency to a component:
The component's dependency is recorded in Compass.
A component can depend on a maximum of 25 other components and it can have a maximum of 100 other components depending on it.
The component dependencies have two visual presentations:
Dependency list: Shows a list of component dependencies recorded in Compass. You can add or remove component dependencies from the dependency list.
Dependency map: A spatial and interactive representation of the component dependencies recorded in Compass. When you add component dependencies in Compass, the dependency map generates a visualization of these dependencies giving you a component-centric view of your software infrastructure. You can traverse the map to view and understand the interdependencies amongst the components.
To view a component’s dependencies:
Component ownership helps assign and identify responsibility for maintaining and operating a component. Having up-to-date ownership information ensures people know who to reach out to for information about that component. Learn more about the importance of adding component ownership
You can view, assign, and change the ownership of your component dependencies from the dependencies list.
If you manage a dependency component with config-as-code, you must use config-as-code to assign ownership for that component. You won't see the Add owner team and Edit owner team options for the component in the dependencies list. Learn how to update your component managed via config-as-code
To add or edit the owner team for a component’s dependencies:
Go to your component’s details page in Compass.
Select Dependencies from the left navigation and stay on the List view.
Select the more actions icon () for the dependency component you want to add or edit the owner team.
For assigning component ownership for a component with no owner team, select Add owner team.
For changing the existing ownership of a component, select Edit owner team.
On the dialog that appears, select an owner team from the list. Then, select Save.
The component owner team’s name appears in the dependency list.
You can remove the record of a component’s dependency on another component from the Dependencies section on the component’s details page.
If you manage your component via config-as-code, you must also use config-as-code to add or remove dependencies. You won't see the Remove dependency option for the component in the dependencies list Learn how to update your component managed via config-as-code
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:
Depends on
Describes the relationship of a component on another component that is necessary for it to operate.
For example, you could describe that an application
component dependsOn
a library
component as part of its build.
Any type of component can depend on any other type of component in Compass.
A component can depend on a maximum of 25 other components and it can have a maximum of 100 other components depending on it.
Rate this page: