For details on Harness' Key Concepts, go to Learn Harness' Key Concepts.
Before you begin using Harness IDP, you should be familiar with the key concepts.
Internal Developer Platform
An Internal Developer Portal (IDP) improves the developer experience in an organization, reduces friction in the software delivery cycle and hides the infrastructure complexity for a developer.
The Golden Path is the opinionated, well-supported and recommend path for build a new software within in an organization. For example, build a backend service, put up a website, create a data pipeline, golden paths to production for new service onboarding.
Software components are typically intimately linked to the source code that constitutes the component, and should be what a developer may regard a "unit of software", usually with a distinct deployable or linkable artifact.
A software catalog is a registry of software components. It is a centralized system that keeps track of ownership and metadata for all the software in your ecosystem (services, websites, libraries, data pipelines, etc). The catalog is built around the concept of metadata YAML files stored together with the code, which are then harvested and visualized in Harness IDP.
Service Onboarding provides self-service workflows that developers use for their platform/DevOps needs, powered by Harness pipelines.
TechDocs is Spotify's homegrown docs-like-code solution built directly into Backstage. Engineers write their documentation in Markdown files which live together with their code - and with little configuration get a nice-looking doc site in their IDP.
Software Catalog in Harness IDP provides a comprehensive framework for defining and managing software entities, including APIs.
The type of API specs that could be added in IDP includes openapi, asyncapi, graphql and grpc.
Is a way to assess new developers' experience and performance while they start doing meaningful code contribution to the codebase since starting in the org, for example time taken by the new developers to merge their tenth pull request.
Describes Templates that developers can use to create new entities. It contains both the parameters that are rendered in the frontend part of the scaffolding wizard (text boxes, auto completes, check-boxes, etc.) and the steps that are executed when scaffolding that component. In Harness IDP Self Service Flows are software templates.
Scorecards is a way to measure software maturity and best practices. Platform engineering personas (DevOps, SRE, Security, etc.) are able to define certain standards as "checks" for different sets of maturity models or standards in their organization. Based on how many best practices a particular software component follows, it gets a score out of 100. The score is used to gamify developers to meet more standards or best practices. It is also used to estimate a confidence on the software by other teams when thinking about using it internally.
Backstage is an open platform for building developer portals. Powered by a centralized software catalog, Backstage restores order to your microservices and infrastructure and enables your product teams to ship high-quality code quickly — without compromising autonomy.
Backstage plugins are used to integrate IDP with different providers for the customization of IDP.
Platform engineering is an emerging technology approach that can accelerate the delivery of applications and the pace at which they produce business value.