Internal Developer Platform  ·  View 04 of 21  ·  People and journeys

Journey — Create and Ship a New Service

The journey the whole platform exists to make possible, and the one place it still hurts.

Editable source SVG draw.io All views
Product Engineer third week on the team Goal — Have a real service serving real traffic before the end of the day Trigger — A story that needs a new component, and a sprint that ends Friday Done when — Running in production, owned, observable, and passing every control 1 · Decide which path 2 · Scaffold one action 3 · Provision ≤ 12 min ◆ moment of truth 4 · Build shared CI 5 · Ship to prod ◆ moment of truth 6 · Own it What they do Picks a golden path Names it and its team Declares a database Writes the actual code Merges to main Adds an alert rule Where Portal catalogue Portal · or CLI Pull request Editor Pull request Component page What the platform does Shows 5 paths Repo · pipeline · IaC Catalog entry Reconciles intent Identity · secret path Builds · signs Advisory verdict Admission check Canary and analysis Wires cost · on-call How it feels Delighted Fine Frustrated Where it hurts Which path fits? Quota refused it Waits on the canary User Journey — Product Engineer Creates and Ships a New Service The trough is a quota rejection during provisioning. It is survivable only because the message names the team's quota and the person who can raise it, rather than returning a cloud error code. v 1.0 · owner Platform Architecture · date 2026-09

The trough

  • A quota rejection during provisioning, at the one moment the engineer has committed to the path and cannot proceed.
  • It is survivable only because the rejection names the team's quota and who can raise it. A provider error code here would send the engineer back to a ticket, which is the failure the platform was built to remove (ADR-04).
  • The canary wait is the second dip, and it is deliberate: automated analysis is cheaper than a rollback at 09:00.

Targets

  • Scaffold to first non-production deploy ≤ 30 min p50, ≤ 2 h p95 (stated assumption).
  • Full golden-path resource set provisioned ≤ 12 min p95; commit to production ≤ 25 min p95.
  • Against an assumed 19-working-day baseline, which is the comparison that justifies the platform's own cost.

What this demands

  • Every error in this journey must be actionable by the engineer without a platform engineer translating it.
  • The advisory verdict must arrive in the pull request within 90 seconds, or engineers stop reading it.
◀  Actors and Their Core Journeys All views Journey — Drive a Change Across 1,400 Components  ▶
Solution Architecture v1.0 · Microsoft Azure · Platform Architecture · 2026-09 · 21 views · 16 architecture decision records04-journey-ship-a-new-service