Contents
In brief
A platform team succeeds when the easiest way to ship is also an acceptable way to operate. That path has to be written down.
Original CloudExchangers explainer. It describes established public practice and labels the desk’s judgment as analysis. It is not a report of a newly announced event.
DevOps, at its best, was a refusal to throw software over a wall. Platform engineering is what that refusal looks like when dozens of teams need the same paved road: source control, build, deploy, observability, identity, and a place to put the service.
What a golden path is
A golden path is the supported way to go from a change to a running service. It is not the only way a determined person can ship. It is the way that already has logging, a deployment identity, a rollback, and someone to ask. The path is a product. If it is slower than the shadow path, people will use the shadow path and you will operate both.
Build it in this order
- Write the contract. What must every service have before it receives traffic? A repository, a pipeline, an owner, a health check, and a dashboard or a log query with a name.
- Make the contract the default. A template repository that includes the pipeline is more honest than a wiki page that asks teams to remember.
- Offer one runtime first. Kubernetes is a common choice because the API is explicit. A managed application service is a fine choice too. Two runtimes on day one is how the platform becomes a brochure.
- Put identity in the template. The pipeline should deploy as itself, with a role that cannot do more than deploy that service.
- Measure the path. Time from commit to production for the template, and the number of services that bypass it. If you do not count the bypass, you do not have a platform. You have a suggestion.
- Staff the exceptions. An exception with an expiry date is a design tool. An exception with no owner is a second platform.
Analysis
Ticket-driven operations feel controllable and scale by hiring. A path feels risky because teams move without a queue. The control moves earlier, into the template and the policy. That is the work. A platform team that only reviews other people’s diagrams has not built a path.
What this guide does not mandate
It does not require Kubernetes, a particular CI product, or a platform team of a certain size. It requires a default that is safe enough to be the easy choice.
References
- Kubernetes overview · Kubernetes
