Definition of the golden path: a recommended and supported route
A golden path is the route that an organisation recommends to its development teams for a common need, and that it commits to maintaining.
Spotify’s engineering blog (engineering.atspotify.com) published, on 17 August 2020 and under the byline of Gary Niemen, an article on how the notion is used within the company. The golden path is defined there as the “opinionated and supported” path to build something: an application service, a website, a data pipeline. In other words, the tool choices have already been made (opinionated) and the route comes with support (supported). A tutorial, per discipline, guides the developer.
The article starts from an observation. Autonomous teams had produced fragmented tooling, where people learned how to do things by asking their colleagues: the author speaks of “rumour-driven development”. With a mapped-out path, he writes, teams do not reinvent the wheel and have fewer decisions to make. The tutorial also serves to onboard new engineers.
The “Platforms” white paper from the CNCF TAG App Delivery (tag-app-delivery.cncf.io) uses the term in a similar sense. A reusable build, test and deployment pipeline, offered with an initial project template and documentation, forms a package often described, according to this text, as a golden path.
Golden path, project template, imposed standard, developer portal: not to be confused
- The project template creates the skeleton of a repository. The path includes it and adds the delivery pipeline, documentation and support.
- An imposed standard closes off other routes. The golden path can be left: in Spotify’s text, the team that departs from it no longer benefits from the same support.
- The developer portal (internal developer portal) is the place where routes are found and read. The CNCF white paper classes web portals and golden paths in two distinct families of capabilities.
- “Paved Road” and “Silver Path” appear in Spotify’s article as derived notions, without being defined there.
These routes are one of the products of platform engineering, defined in a separate entry.
Choices already made, support provided
The two adjectives in the definition say what a golden path contains.
The choices concern tools and how they fit together: language, delivery pipeline, resources described by infrastructure as code, deployment mode, for example with GitOps. Spotify’s article asks that the recommended tools be easy to discover and that the journey from one to the next be clear.
Support covers, in the same article, quality instructions, an obvious place to turn for anyone who gets stuck, and a tutorial updated each time a tool on the route is replaced.
A media group maps out its first path
Imagine a media group in which several teams develop the services behind its websites. Each has chosen its language and set up its delivery pipeline. The platform team picks a recurring need, the web service exposing a programming interface, and maps out its path: repository template, delivery pipeline, on-demand environments, tutorial, support channel.
The team in charge of podcasts needs audio processing that the path does not cover. It departs from the path for this component and takes on its operation. If other teams make the same departure, the platform team reads it as the need for a second path.
The limitations of a golden path
Spotify’s article points out several difficulties. A tutorial considered too long reflects a route that is too long: it is the route that needs shortening. A heavily simplified route hides black boxes, whereas the tutorial also has an educational purpose. Finally, spreading ownership of the content across many teams creates a coordination problem.
Our page DevOps and platform engineering describes how these paths are designed within an internal developer platform.