paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 40 Packages Projects Releases Wiki Activity

Clarify that we start by only implementing the Component entity

Browse Source
This commit is contained in:
Marc Bruggmann
2020-06-01 17:06:00 +02:00
parent 1312d34147
commit 37ca9e1434
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture-decisions/adr005-catalog-core-entities.md
+4 -2
View File
@@ -10,7 +10,7 @@ We want to standardize on a few core entities that we are tracking in the Backst
## Decision
We maintain a catalog of the following core entities:
Backstage should eventually support the following core entities:
* **Components** are individual pieces of software
* **APIs** are the boundaries between different components
@@ -18,6 +18,8 @@ We maintain a catalog of the following core entities:
![Catalog Core Entities][catalog-core-entities]
For now, we'll start by only implementing support for the Component entity in the Backstage catalog. This can later be extended to APIs, Resources and other potentially useful entities.
### Component
A component is a piece of software, for example a mobile application feature, web site, backend service or data pipeline (list not exhaustive). A component can be tracked in source control, or use some existing open source or commercial software. It can implement APIs for other components to consume. In turn it might depend on APIs implemented by other components, or resources that are attached to it at runtime.
@@ -72,4 +74,4 @@ spec:
## Consequences
We will start with fleshing out support for the Component entity in the catalog, and expand to APIs and Resources later down the line.
We will continue fleshing out support for the Component entity in the Backstage catalog.