Backstage

New developer accesses Backstage portal.

Uses the software catalog to discover existing services and components.

Uses software templates to create a new microservice with pre-configured dependencies.

Accesses TechDocs to learn about best practices and coding standards.

Integrates with CI/CD pipelines for automated testing and deployment.

Developer selects a software template for a microservice.

Provides necessary parameters, such as service name and description.

Backstage generates the initial code and configuration files.

Developer customizes the code and integrates with existing APIs.

Deploys the microservice to a Kubernetes cluster.

Developer accesses the infrastructure management section of Backstage.

Requests a new database instance with specific configurations.

Backstage provisions the database and provides connection details.

Developer integrates the database with their application.

Monitors the database performance through Backstage.

Developer uses the search function in Backstage to find documentation on a specific topic.

Backstage aggregates documentation from various sources, such as Git repositories and Confluence.

Developer reviews the documentation and provides feedback.

The documentation is automatically updated based on the feedback.

Backstage integrates with security scanning tools to identify vulnerabilities.

Vulnerabilities are displayed in the software catalog.

Developers are notified of vulnerabilities in their components.

Developers use Backstage to remediate the vulnerabilities.

The security scanning tools automatically verify the fix.