Platform engineering
A path a developer can use without a ticket: templates for the usual deploy, and an engineer who can stay while the team adopts that path.
Who this is for
- Product teams that still file a ticket for every environment
- A platform team that needs another engineer
- A team that has a cluster and no standard way to deploy to it
The usual way to ship
Templates and a path for the deploy most teams need. The unusual case can still leave the path.
The runbook for that path
How to deploy, and what to do when a deploy fails in one of the common ways.
An engineer on the team
On the team for the weeks or months it takes to make the path the normal way to ship. A path with an end is a scoped project, and it ends with a handoff.
Capabilities
- Templates for the usual deploy
- A golden path, with a way out for the unusual case
- Runbooks for that path
- An engineer on the team while it is adopted
Common questions
Do we need Kubernetes for a golden path?
No. The path can deploy to Kubernetes, ECS, or virtual machines. It is about the steps a developer takes, not the runtime underneath.
Can you stay after the path exists?
Yes, as an embedded engineer for as long as it is useful. If the work has a clear end, it is a scoped project that ends with a handoff.