Services

Resources

Company

Platform engineering

Platform engineering is the discipline of designing and running an internal developer platform (IDP). An IDP is a self-service layer of tools, templates and APIs that lets product teams create services, environments and deployments without filing tickets. A platform team treats this platform as a product, with developers as its customers.

How it works

The platform team picks a small set of supported paths, often called golden paths, and automates them end to end. For example, a developer runs one template that creates a repository, a CI pipeline, a Kubernetes namespace, dashboards and alerts. A request that used to take three days of tickets then takes ten minutes. The team tracks adoption and developer feedback the same way a product team tracks users.

Why it matters in production

Without a platform, each team rebuilds the same pipelines and infrastructure in its own way. Senior engineers become a bottleneck for every deploy question. A good platform reduces cognitive load and makes secure defaults the easy choice. A platform nobody asked for gets bypassed, so adoption has to be earned.

See also

On the One2N blog

References

  1. CNCF platforms white paper

  2. Team Topologies key concepts

Comic about platform engineering: Kai waits three days on five tickets while Asha has 40 in her queue; one template command creates repo, CI, namespace, dashboards and alerts in 10 minutes; Noor tracks adoption and Kai's Postgres request ships in template v2.