liveBook · Manning

Golden path

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A paved road is a recommended, supported software-delivery path that provides developers with a convenient default implementation route.

Starting a new application should not require months of coordination or a choice between a deadline and a suitable architecture. A golden path, also called a paved road, gives developers a supported route from a new application to production while incorporating the organization’s quality, security, and compliance requirements. section 13.1.1 section 13.2.1

Think of the path as a recipe: automate it where practical, and document any remaining manual steps. A path for a new Java API might establish repositories, infrastructure, and common libraries according to organizational conventions. As part of an internal developer platform, such paths make common tasks easier to perform without requiring every team to assemble its own route. section 13.2.1 section 13.6

A neobank’s paved road

At a mobile-first neobank, a developer used a platform CLI to answer a few questions and start a new microservice. The path typically took a service to production in less than a few hours. The platform supplied many defaults without hiding Kubernetes entirely—a deliberate balance between convenience and the ability to understand what is running. section 13.2.1

A path that extends into operations

La Redoute’s path includes self-service provisioning for pipelines, secrets, configuration, and service exposure. Its pipeline supports progressive deployments, while components provide foundations for logs and metrics. The route therefore supports teams beyond initial creation, into operating services in production. section 13.3

Keep the path useful rather than treating it as a mandate:

  • Check domain boundaries before creating another service. Cheap provisioning can encourage too many highly coupled microservices. section 13.1.1
  • Improve the platform incrementally in response to developer needs; a small set of standard pipelines can precede a fuller portal. section 13.3 section 13.6
  • Do not assume every organization needs an internal developer platform. Consider team count, likely adoption, and whether existing offerings suffice. section 13.6

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Defines a path as an automated or documented recipe and illustrates its workflow, without providing implementation code.
Examples
Uses a neobank’s CLI-provisioned microservices and La Redoute’s self-service pipelines, secrets, configuration, and operational foundations.
What you can do after
Apply it via an internal developer platform to make application setup and deployment self-service while retaining production requirements.
How it connects
Connects internal developer platforms, developer experience, continuous delivery, domain boundaries, and production observability.

Also explained in

Compare how 2 books explain golden path →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.