API Gateway Platform · View 05 of 21 · People and journeys
The finding
- The first trough is that a 1% canary on a low-traffic route may never produce a statistically meaningful signal — the rollout looks healthy because nothing happened. This is left open as Core Architecture Question 7 and ADR-13.
- The second trough is not technical: two organisations will not migrate by the sunset date. The platform's answer is a dated per-tenant version pin with an owner, not a slipped date for everyone.
- Sunset is gated on evidence of zero active callers, or on a recorded override with a name against it.
Assumptions
- At most three live versions per API, two in the MVP.
- Canary steps 1% → 5% → 25% → 100%, automatic rollback within 90 s of a breaching signal (assumption).
Risks
- Deprecation headers are machine-readable and largely unread. The portal's active-caller view is the mechanism that actually moves people, which is why it is an MVP item and not Phase 2.
