A component in Atlassian Compass is one of the building blocks your team creates, manages or maintains, such as a service, application, data pipeline, dashboard, library or machine learning model. Each component is owned by a dedicated team, and Compass tracks how components depend on one another and scores their health and readiness.
In software development, managing services, applications, and other key components can be complex. Atlassian Compass simplifies this by offering a clear and unified way to manage all the individual building blocks, called components, that make up your software.
A component in Compass represents everything your team creates, manages, or maintains: services, applications, data pipelines, dashboards, libraries, or machine learning models. Each component is owned and maintained by a dedicated team.
To make the concept of Compass Components easier to understand, think of them as parts of a car:
| Real-World Object | Compass Component |
|---|---|
| Car | Application or Service |
| Engine | Microservice |
| Fuel Line | Data Pipeline |
| Dashboard | Monitoring Dashboard |
| Owner’s Manual | Documentation |
| Mechanic | Team responsible for the component |
| Toolbox | Library or Utility |
| Street Signs | API Endpoints |
Just like in a car, each component plays a specific role in the overall software, and they work together to deliver the full product.
The Compass component catalog brings all these pieces together in one place. The catalog shows key details for each component, such as the name, description, owner, and other important attributes. It also links to essential resources like code repositories, Jira projects, documentation, and dashboards.
With Compass, teams can easily find and manage everything related to a component, all in one location.
Components in software development are rarely isolated. They depend on each other. For example, a microservice may rely on a data pipeline to function, or a machine learning model might need specific datasets to operate. Compass tracks these relationships, making it easy for teams to see how components interact and depend on one another.
Development managers gain several benefits from Compass:
Here are some key examples of component types in Compass, with simple analogies:
Compass simplifies the complexity of managing distributed software components. It gives development managers a clear view of how components fit together, who is responsible for each one, and how well they are performing. This makes it easier to ensure that teams are following best practices and maintaining the health of the software.
In many organizations, different teams manage different components. Compass centralizes information about each component, making it easier for teams to collaborate without confusion. It provides a unified view of who owns what, how components interact, and the overall status of the project.
Atlassian Compass offers development managers a central platform to manage the complexity of distributed software components. It simplifies ownership, improves visibility into component health, and enhances collaboration between teams. With Compass, managing software components becomes more efficient, allowing teams to build high-quality software without the usual headaches of disconnected systems.