DESOSA 2022

Backstage

Backstage is a centralized software catalog, which allows you to manage all your software, all in one place. By centralizing services and standardizing your tooling, Backstage streamlines your development environment from end to end.

The main features Backstage offers are:

  • Easily spin up a new microservice with your organization’s best practices built-in
  • Easily customize new projects with your best practices baked-in
  • Automatically generate documentation
  • Push-button deployment
  • All your service’s deployments in one, aggregated view
  • Cloud agnostic

The Backlog ideology can be described using the following statements:

  • Build an ecosystem, not a wilderness
  • Metadata on tap
  • Discoverability & accountability
Project Site | Project Source

Authors

Aaron van Diepen

Computer Science masters student @TU Delft, 5 years of experience in Software Development and Testing, sustainability, graphics and loads of other things!

Daan Groenewegen

First year Computer Science Master student at TU Delft. Previous work experience in camera software and object detection. Interested in the nature of Open Source projects.

Philip Groet

Embedded Systems masters student @TU Delft, active at multiple software and engineering companies, interested in web development and Electrical Engineering.

Thijs Verreck

CoSEM master student @ TU Delft. Interested & experienced in Conversational AI & Data ethics.

Backstage - Scalability, Maintainability & Extensibility

Scalability in Backstage One of the potential benefits from using Backstage is that it enables extensibility and scalability by letting you easily integrate new tools and services (via plugins), as well as extending the functionality of existing ones. Backstage, as described by its creators, is more like a visual tool for managing services in cloud platforms that also holds the documentation for those services. By then using cloud clusters to run Backstage, which can be entirely split up into separate services, it enables Backstage to become a fully scalable system.
Backstage
March 28, 2022

Backstage - Quality and evolution

Quality and evolution We already have discussed the vision behind Backstage and the architecture that makes up the Backstage product. In this essay we talk about the quality control of Backstage and how the project is evolving. Key attributes The key attributes for Backstage can be divided into two categories: external qualities and internal qualities. We will first discuss the systems internal quality attributes and afterwards discuss the external attributes.
Backstage
March 21, 2022

Backstage - From Vision to Architecture

From vision to architecture The first essay gave a description of the vision of Backstage. It states how Backstage is aimed at building developer portals. This essay will build on top of the first one, and explore what the architecture of Backstage looks like. The analyses in this essay range from the main patterns used up till the containers and development views. Main architectural pattern The main architectural pattern used by Backstage is a common one for web applications.
Backstage
March 14, 2022

Backstage - Product Vision and Problem Analysis

Product vision and problem analysis Backstage is an open platform that can be used to build developer portals. It is used by companies to give developers a platform that can store information about their tooling, data, software components and documentation. It aims to give back control of the infrastructure to the developer. Backstage does this through three main elements: a software catalog, software templates and a documentation platform (TechDocs). The software catalog is used to manage all of the company’s software.
Backstage
March 7, 2022

Contributions

Implement code changes as suggested by analysis tools

backstage/backstage

This Pull Request implements suggested changes by DeepSource. The changes (and their explanations) are:

  • double non-null assertion operators

a non-null variable can not suddenly turn into null, most likely the writer thought he was doing boolean conversion

  • unexpected awaits for non-promise values

might give the illusion that a function returns a promise while it does not

open
Open PR