Advanced Vocabulary for Platform Engineers

Platform engineering has emerged as a discipline focused on building and maintaining internal platforms that improve developer productivity. The vocabulary of platform engineering blends software architecture, organisational theory, and product thinking. This guide covers the essential terms you need to discuss platform engineering fluently in English.

What Is Platform Engineering?

Platform engineering is the practice of designing, building, and operating self-service internal developer platforms (IDPs) that enable product teams to deliver software faster and more reliably. Unlike traditional DevOps, which often relies on shared operations teams, platform engineering treats the platform itself as a product with internal developers as its customers.

“Our platform engineering team owns the IDP. Product squads provision environments, run pipelines, and deploy services without ever raising a ticket with the infrastructure team.”

Internal Developer Platform (IDP)

An Internal Developer Platform (IDP) is a curated set of tools, workflows, and self-service capabilities that developers use to build, test, and deploy software. An IDP typically includes environment provisioning, CI/CD pipelines, secrets management, observability, and service catalogues.

“The IDP abstracts away Kubernetes complexity. Developers define what they want to deploy; the platform handles how it gets deployed.” “Adoption of the IDP increased from 40% to 85% after we added a service catalogue and reduced the number of steps to deploy a new service from twenty-three to four.”

Golden Paths

A golden path (also called a paved road) is an opinionated, pre-built, well-supported route for common developer tasks. It is not mandatory, but it is the easiest path — and the one the platform team actively maintains and improves.

“Our golden path for a new microservice gives you a repository template, a CI/CD pipeline, observability dashboards, and a runbook — all configured and connected — in under ten minutes.” “We don’t block teams from going off the golden path, but they take on operational responsibility for anything they build outside it.”

Paved Road

Paved road is a synonym for golden path, popularised by Netflix. The metaphor is simple: you can travel off-road if you want to, but the paved road is faster, smoother, and better maintained.

“Netflix’s paved road gave teams pre-integrated libraries for resilience, observability, and deployment. Teams that stayed on the paved road shipped faster and had fewer incidents.”

Developer Portal

A developer portal is the front end of an internal developer platform — a web interface where developers discover services, documentation, tools, APIs, and self-service workflows. Backstage (by Spotify) is the most widely adopted open-source developer portal.

“The developer portal is the front door to the platform. From there, engineers can scaffold a new service, browse the service catalogue, view ownership, and check deployment status.” “We integrated our API documentation, runbooks, and incident history into the developer portal so everything is in one place.”

DORA Metrics

DORA metrics — from the DevOps Research and Assessment group — are four key metrics used to measure software delivery performance:

• Deployment frequency — how often code is deployed to production
• Lead time for changes — time from code commit to production
• Change failure rate — percentage of deployments that cause a production incident
• Time to restore service — how long it takes to recover from a failure

“Our DORA metrics improved significantly after adopting the platform. Deployment frequency went from weekly to daily, and lead time dropped from four days to six hours.” “High-performing teams in the DORA report deploy multiple times per day and restore service in under an hour. That is our target state.”

Team Topologies

Team Topologies is a framework (from the book by Matthew Skelton and Manuel Pais) for organising software teams to optimise for fast flow of change. It defines four team types:

• Stream-aligned team — aligned to a flow of work for a product or service
• Platform team — provides self-service capabilities to stream-aligned teams
• Enabling team — helps other teams adopt new technologies or practices
• Complicated-subsystem team — owns a subsystem requiring deep specialist knowledge

“We restructured using Team Topologies. Our cloud infrastructure team became a platform team; the product squads became stream-aligned teams. The interaction mode changed from tickets to self-service APIs.”

Cognitive Load

Cognitive load refers to the mental effort required of a developer to understand, operate, and maintain a system or workflow. Platform engineering aims to reduce the cognitive load on product teams by abstracting infrastructure complexity.

“Before the platform, developers had to understand Kubernetes manifests, Helm charts, Terraform modules, and Vault secrets just to deploy a service. That cognitive load was too high.” “A good golden path reduces cognitive load by making the right thing the easy thing.”

Platform Adoption

Platform adoption measures how widely internal teams use the platform. Low adoption often indicates that the platform is too complex, too slow, or does not solve real developer problems. Platform teams measure adoption as a key product metric.

“We track platform adoption by service: what percentage of services use the standard pipeline, the standard logging library, and the service catalogue registration.” “Adoption is a lagging indicator. To drive it, we focus on reducing friction — every extra step in onboarding costs us adoption.”

Practical Phrases for Platform Engineers

• “We need to reduce cognitive load on stream-aligned teams — they should not need to know how Terraform works.”
• “The golden path is the default; teams can deviate, but they own the consequences.”
• “Our DORA metrics tell us where the bottlenecks are. Lead time is high because of long review queues, not slow deployments.”
• “Developer portal adoption is at 60%. The main barrier is that the service catalogue data is stale.”
• “We’re applying Team Topologies to clarify interaction modes — the platform team provides X-as-a-service; we don’t do bespoke work for each team.”

Platform engineering vocabulary reflects a shift from reactive operations to proactive, product-led infrastructure. Mastering these terms will help you contribute to platform strategy discussions, evaluate IDP tooling, and communicate the value of platform engineering to engineering leadership and business stakeholders.