Helping, Not Forcing
If you can't build a perfect abstraction, how do you guide developers to do the right thing without mandating it?
The concept of Golden Paths (coined by Spotify) — also known as Paved Roads (Netflix) — is a philosophy for platform adoption. It answers the question: how do you get hundreds of developers to follow best practices without writing a policy document nobody reads?
A Golden Path is an opinionated, supported, and highly automated way of building and deploying software. It embodies your organization's best practices for security, reliability, and observability, packaged into a workflow so easy that choosing it is the obvious decision.
The Path of Least Resistance
Crucially, a Golden Path is not mandatory. Developers are free to go "off-road" and build their own custom infrastructure if they have a unique need. The platform team does not block them.
However, the Golden Path is designed to be the path of least resistance — and the path of least risk.
| On the Golden Path | Off-Road | |
|---|---|---|
| Setup time | Minutes (automated scaffolding) | Days or weeks |
| Security | Pre-configured, policy-compliant | Your responsibility |
| Monitoring | Included by default | You build it yourself |
| On-call support | Platform team supports you | You're on your own at 3 AM |
| Upgrades | Platform team handles them | You handle them |
Most developers just want to ship features. Given this choice, they will almost always choose the easy, supported Paved Road over the hard, unsupported jungle path. Compliance and best practices become the default outcome — not through enforcement, but through incentive design.
What a Golden Path Looks Like in Practice
A developer runs a single command or fills out a short form in an internal developer portal:
platform new service --name payments --language go --database postgres
Within minutes, they have:
- A Git repository with a standard project structure
- A CI/CD pipeline pre-configured with security scanning and automated tests
- A Kubernetes namespace with resource quotas and network policies applied
- A PostgreSQL database provisioned with encrypted storage and automated backups
- Dashboards and alerting pre-wired in Grafana
- Runbook templates in the team's wiki
None of this required the developer to understand Kubernetes, Terraform, or AWS IAM. They got all of it because they chose the Golden Path.