Kind Application

An application is a crucial entity within the T-matic platform and represents the runtime execution of a software component. It can be thought of as a running instance of a component, where the code and logic encapsulated by the component are actively used to fulfill specific tasks or functions.

Example Descriptor for Application

apiVersion: backstage.io/v1alpha1
kind: Application
metadata:
  name: ecommerce-app
  description: E-commerce website
spec:
  type: website
  lifecycle: production
  owner: ecommerce-team
  system: ecommerce-website
  dependsOn:
    - resource:default/ecommerce-website-cluster
    - resource:default/ecommerce-website-database

Application Structure

• apiVersion and kind [required]:

  • Must be set as backstage.io/v1alpha1 and Application.

• spec.type [required]:

  • Specifies the application's type, such as "web-app" or "mobile-app."

• spec.lifecycle [required]:

  • Describes the lifecycle phase of the application, be it "production", "experimental", or others.

• spec.owner [required]:

  • Points to the owning entity, providing clarity on responsibility within T-matic.

• spec.system [optional]:

  • Relates the application to a specific system or overarching solution within the organization.

• spec.dependsOn [optional]:

  • Highlights other applications, components, or resources that this application requires.

Considerations

1. The T-matic software catalog supports a diverse set of values for the type and lifecycle fields, but consistency and standardization are key for organizational clarity.

2. The owner typically references the team or department overseeing the application's development, maintenance, and updates.

3. Fields like system, and dependsOn help outline the application's position and dependencies within the broader organizational ecosystem.