TL;DR
Golden Paths v3: Multi‑Runtime Templates and Test Orchestration without the fluff: focus on outcomes, measure them, and stop pretending slides are progress.
Why v3 Golden Paths?
APIs were just the start. Teams run batch jobs, event workers, data pipelines, and serverless functions. Golden paths v3 add multi‑runtime support plus opinionated test orchestration so quality keeps pace with velocity.
Multi‑Runtime Templates
- HTTP API: REST/GraphQL with CI/CD, telemetry, and GitOps manifests
- Event Worker: Queue/Kafka consumers with KEDA scaling and idempotency helpers
- Batch: Scheduled jobs with retries, checkpoints, and cost controls
- Data Pipeline: ETL with lineage and data quality checks baked in
- Serverless: Functions with cold‑start warmers, IAM least privilege, and API gateway wiring
Test Orchestration as a First‑Class Capability
- Contract tests: Provider/consumer checks for APIs and events
- Env orchestration: Ephemeral test envs per PR with seeded data
- Performance tests: Golden signal thresholds and SLO checks in pipelines
- Security tests: SAST/DAST/IaC scans and policy gates
Example: Backstage Template Fields
- Service/runtime type, owners, SLO class, data store choice
- Opt‑in modules: feature flags, cache, queue triggers
- Auto‑generated repos: app + config (manifests), dashboards, runbooks
Adoption Plan
- Inventory common runtimes and build templates for top three
- Add test orchestration primitives; standardize data seeding
- Publish docs and workshops; measure lead time and failure rates
Conclusion
Golden paths v3 reduce cognitive load across more workloads—and raise quality with integrated tests and environments.
“Make Golden Paths v3: Multi‑Runtime Templates and Test Orchestration boring: repeatable, measurable, and rehearsed.”
Long‑Form Addendum: Making Golden Paths v3: Multi‑Runtime Templates and Test Orchestration Feel “Obvious” to Teams
“Good platforms remove decisions; they don’t add dashboards.”
1) Start With a Promise
Write a one-paragraph promise to engineers: what the platform guarantees (templates, security defaults, observability, rollbacks) and what it requires (standards, ownership, on-call discipline). Publish SLOs for the platform itself so teams can trust it.
2) The Golden Path Mechanics
- Scaffold: a template creates repo, pipeline, service skeleton, and dashboards.
- Guardrails: policies are enforced in CI/CD and at deploy time.
- Self-service: teams can create a service, namespace, secrets, and alerts without opening a ticket.
- Upgrades: templates carry upgrades forward; deprecations are announced with timelines.
3) What to Measure (Outcomes)
- Time to first deploy for a new service
- Lead time for change and change failure rate
- Platform ticket volume per team and time-to-close
- % of services on the default path and number of exceptions
- OKR progress tied to business outcomes (availability, onboarding speed)
4) Common Failure Modes
- Too many options: teams choose differently and you can’t support it. Fix with fewer, better defaults.
- Optional policies: “recommended” guardrails become ignored. Fix by enforcing with clear remediation.
- No ownership: nobody owns migrations or breaking changes. Fix with product ownership and a deprecation policy.
5) Checklist
- One default template exists per service type (API, worker, UI).
- Exceptions are time-bound and visible.
- Platform publishes SLOs and a changelog.
- Monthly review: adoption, tickets, and incident learnings feed back into templates.
Glossary (Tooltips)
- IDP: Where templates, guardrails, and paved roads live.
- DX: What improves when you remove toil and ambiguity.
- CI/CD: The path from commit to production.
- SLO: How you keep the platform honest.
- OKR: Helps align platform work to outcomes.
Appendix 1: Making the Standard Path the Fast Path
A Practical Product Loop
Platforms win by compounding: every week you make the default path easier and the exception path more expensive.
- Pick 1–2 templates as “blessed defaults.”
- Add guardrails in CI/CD and at deploy time, with actionable errors.
- Publish a changelog and deprecation policy so teams trust upgrades.
- Review adoption and exceptions monthly; prioritize work that reduces repeated tickets.
30/60/90 (Adoption and Reliability)
- 30 days: define platform SLOs; ship one golden path with docs + runbook; measure baseline tickets and lead time.
- 60 days: add self-service for the top ticket categories; introduce an exception registry (owner + expiry).
- 90 days: enforce defaults for new services; migrate the highest-risk legacy patterns; tie outcomes to OKRs.
Checklist
- One obvious default path exists (and it works reliably).
- Exceptions are time-bound and visible.
- Feedback loops exist: office hours, a roadmap, and real metrics.
Appendix 2: Making the Standard Path the Fast Path
A Practical Product Loop
Platforms win by compounding: every week you make the default path easier and the exception path more expensive.
- Pick 1–2 templates as “blessed defaults.”
- Add guardrails in CI/CD and at deploy time, with actionable errors.
- Publish a changelog and deprecation policy so teams trust upgrades.
- Review adoption and exceptions monthly; prioritize work that reduces repeated tickets.
30/60/90 (Adoption and Reliability)
- 30 days: define platform SLOs; ship one golden path with docs + runbook; measure baseline tickets and lead time.
- 60 days: add self-service for the top ticket categories; introduce an exception registry (owner + expiry).
- 90 days: enforce defaults for new services; migrate the highest-risk legacy patterns; tie outcomes to OKRs.
Checklist
- One obvious default path exists (and it works reliably).
- Exceptions are time-bound and visible.
- Feedback loops exist: office hours, a roadmap, and real metrics.
Appendix 3: Making the Standard Path the Fast Path
A Practical Product Loop
Platforms win by compounding: every week you make the default path easier and the exception path more expensive.
- Pick 1–2 templates as “blessed defaults.”
- Add guardrails in CI/CD and at deploy time, with actionable errors.
- Publish a changelog and deprecation policy so teams trust upgrades.
- Review adoption and exceptions monthly; prioritize work that reduces repeated tickets.
30/60/90 (Adoption and Reliability)
- 30 days: define platform SLOs; ship one golden path with docs + runbook; measure baseline tickets and lead time.
- 60 days: add self-service for the top ticket categories; introduce an exception registry (owner + expiry).
- 90 days: enforce defaults for new services; migrate the highest-risk legacy patterns; tie outcomes to OKRs.
Checklist
- One obvious default path exists (and it works reliably).
- Exceptions are time-bound and visible.
- Feedback loops exist: office hours, a roadmap, and real metrics.