Skip to content
matthewcm.dev

    ↑ ↓ move · ↵ open · tab scopeopen graph →

    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.

    Growingtended planted 2 min read
    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.

    My first one

    The first golden path I built was a Web Accelerator at Elanco: web standards baked into a boilerplate, provisioned through the company’s self-service portal, with shared Storybook components, across a web estate of 80 sites (Building a Web Platform for 80 Sites). Its biggest lesson is the one above: keep the shared parts in versioned packages, because copied templates drift.

    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
    • Books That Shaped How I BuildGrowing
      …ork as a production system and designs the paths work actually takes, so nobody has to be a hero. That's what Golden Paths and DORA Metrics are for, and why You Can't Serve Two Masters.
    • Building a Web Platform for 80 SitesGrowing
      Looking back, this was platform engineering before I had the words for it: a golden path, self-service provisioning and a shared component layer, all in a supporting domain (Where Platforms Fit: DDD Subdomains). It's als…
    • Cloud Platform TranslatorsSeed
      Related: Internal Developer Platform · Golden Paths · Platform Strategy
    • Digital Culture Is Built from HabitsGrowing
      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…
    • Explore, Expand, ExtractSeed
      Related: Internal Developer Platform · Golden Paths · Platform Strategy
    • Golden Paths and the Recommended RoutineGrowing
      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.
    • Growing a Platform: Breadth, Depth and Gear ShiftingGrowing
      Related: Internal Developer Platform · Golden Paths · Web Accelerator · Platform Strategy
    • Infrastructure as Code for People, Not Just ServersGrowing
      …top, clones one repo, runs one command, and by lunch they can build, test and run the main services. That's a golden path for devices. It's the same idea as the Web Accelerator I built at Elanco for new web projects: put…
    • 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)
    • Low-Code Platforms: Where Do They Belong?Seed
      Related: Golden Paths · Internal Developer Platform · What Makes an AI Agent
    • Skill Trees as Platform Capability MapsGrowing
      …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…
    • Web AcceleratorGrowing
      It's a golden path for websites: the easy way and the standard way are the same way. Standards stop being a document people forget and become defaults they get for free. And it makes consolidation possible later, because…

    ↪ Links to (6)