Single EU region for routing v2 launch
Context
order-routing-v2 needs a launch posture. Multi-region is technically possible but adds 6 weeks and significant operational surface area. Customers split: acme-logistics is US-east; stellar-freight is EU; northwind-supply is US-east.
Decision
Launch in a single EU region (Frankfurt). US customers are routed via cross-region replication for v2; multi-region is phase 2 (Q3 or Q4 depending on demand).
Why
- Devon's on-call rotation overlaps Sydney + London hours — easier to support EU primary.
- Cross-region replication is a known quantity; we've run it for billing for 18 months.
- The 6-week multi-region delay would push the GA past the acme-logistics renewal trigger date.
Consequences
- US-east customers see ~30ms cross-region latency added; still well within the <200ms target.
- Multi-region is on the Q3 strategy doc as a follow-on; not committed yet.
Backlinks · 3
↪meetings/2026-04-14-staff-roadmap…Maya joins for product context. ## Decisions - Confirmed single-region-eu as the v2 launch posture. - Audit log ([[projects/audit-log…↪people/devon-kim…owner) - use-protobuf-internal (co-decider) - single-region-eu (decider) - 2026-04-22-q2-planning ## Notes…↪projects/order-routing-v2…internal RPC moves to protobuf; JSON only at the edge - single-region-eu — one EU region for v2 launch; multi-region phase 2 - [[dec…