Golden Path
A Golden Path is a fully supported, platform-team-curated standard route for a common development task — for example, creating a new microservice, adding a feature flag, or provisioning a database. It bundles best practices, security standards, and tooling into a single, frictionless path.
The Golden Path is not mandatory: teams may deviate from it, but lose the platform team's active support guarantee in doing so.
Core Concept
- Curated, not mandated: The path is easier than the alternative, not enforced.
- Batteries included: Security configurations, logging, monitoring, and tests are integrated from the start.
- Self-Service: Developers launch a new service in minutes, without waiting for an ops team.
- Paved Road: The metaphor: we build a paved road. Going off-road is possible, but slower.
Components of a Golden Path
- Service Template (Cookiecutter/Backstage): A pre-configured code template with all necessary configurations.
- CI/CD Pipeline: A ready-made pipeline with security scanning, tests, and deployment.
- Observability: Standardised logging, tracing, and alerting are active by default.
- Documentation: The path is self-documenting and easy to find in the Internal Developer Portal (IDP).
Focus: Reduce Cognitive Load
Developers should spend their energy on their domain problem, not on infrastructure boilerplate.
FAQ
What is the difference between a Golden Path and standardisation?
Standardisation enforces a single way. The Golden Path is the recommended, well-supported route from which teams can deviate for good reason. It creates incentives rather than prohibitions.
Who maintains the Golden Path?
The platform team. Maintaining it is one of their core responsibilities. An outdated Golden Path is worse than no Golden Path.
Reference Guide
- Backstage: The leading open-source tool for Internal Developer Portals. backstage.io
- Platform Engineering: platformengineering.org
- Team Topologies: Conway's Law and platform teams. teamtopologies.com