Golden Paths
The opinionated, fully supported route from nothing to a running service. Optional, but so much easier than the alternatives that teams choose it.
On this page
A golden path (Spotify’s term; Netflix calls it the “paved road”) is the opinionated, supported default for a common task, such as creating a new service. It bundles the best-practice choices so teams don’t have to make them again.
What a good one includes
A good golden path takes a team from nothing to a deployed service in one step: repository, CI pipeline, logging, dashboards, alerts and on-call wiring, all already connected. It’s usually delivered as:
- Templates: Backstage software templates, cookiecutter, a
create-*CLI. - Reusable modules the template references: infrastructure modules, Helm charts, shared CI templates.
- Documentation that explains the choices, so people can make informed exceptions.
Optional but attractive
The defining property: teams can go off-road, but then they own the extra work. Adoption is earned by being the easiest option, not mandated. A golden path that has to be enforced is a sign it isn’t golden.
Keep them thin and versioned
The most common failure is a template that forks into every service and then rots. Prefer thin templates that reference shared, versioned modules, so improvements flow to existing services instead of only to new ones.
Anti-patterns
- A golden path only the platform team understands.
- Mandating it without measuring whether teams actually find it faster.
- Templates with no upgrade path once a service has been generated.
- Paving every road. Golden paths belong to common, supporting work, not to the core of what teams build. See Where Platforms Fit: DDD Subdomains.
For agents too
Golden paths matter even more when some of the “developers” are AI agents. An agent on a well-paved road (one template, clear conventions, fast feedback) is far more reliable than one improvising infrastructure. See What Makes an AI Agent.
A training parallel
In calisthenics, a well-designed beginner routine does the same job. It’s not the only way to train, but it bundles sensible choices so you can start immediately and deviate once you know why. The full metaphor is in Golden Paths and the Recommended Routine, and the platform side in Internal Developer Platform.
- #platform-engineering
- #golden-paths
- #developer-experience
- #templates
↩ Linked from (4)
Make the good routine the default. A golden path that creates a service with CI, tests, observability and security scanning already wired in turns best practice into the path of least resistance. See Golden Paths and the…
A golden path is the platform version: an opinionated, supported default that takes a team from nothing to a deployed, observable service without making fifty decisions. Repo, CI, logging, dashboards, alerts — one step.
- Internal Developer PlatformGrowing
Service scaffolding (Golden Paths) CI/CD and environments Infrastructure provisioning, often through infrastructure-as-code modules Secrets management and access control Observability wired in by default (Observability)
…management, observability | | Applied skills | freestanding hold, straddle work | self-service environments, Golden Paths for common services | | Advanced | press to handstand | ephemeral preview environments per PR, po…
↪ Links to (4)
Related by topic
- Growingcase study
Building a Low-Code BPMN Workflow Platform
Frontend craft - Growing
Calisthenics Programming: Skill vs Hypertrophy Phases
Calisthenics Lab - Seed
Convex
Frontend craft - Seed
Deep Learning
Platform engineering