Scale beyond the measured single-active v1 capacity envelope #29

New Issue

2026-07-16T22:17:18+02:00

Kyuubi commented

2026-07-16 22:17:18 +02:00

Parent: #1
Identified by: #23
Depends on the architecture decision in the HA/shared-state follow-up when horizontal scale is selected.

Classification

Post-v1. The only supported v1 envelope is the versioned single-active profile in the capacity documentation.

Trigger

Start this work when a valid 30-day peak cannot be served with 50% headroom, sustained CPU/memory/state depth crosses the documented thresholds, or product targets exceed the measured envelope.

Outcome

Measure the real bottleneck, select vertical or horizontal scaling from evidence, and publish a new versioned capacity/topology claim.

Acceptance criteria

Production traffic shape and bottleneck evidence are captured without endpoint/player retention.
New state, limiter, queue, and latency budgets fail closed under overload.
At least 150% of the intended peak passes endurance, failure, recovery, and rollback gates.
Any horizontal design proves deterministic mediator routing and shared-state safety.
The prior envelope remains documented and no unmeasured capacity claim is published.

Parent: #1 Identified by: #23 Depends on the architecture decision in the HA/shared-state follow-up when horizontal scale is selected. ## Classification Post-v1. The only supported v1 envelope is the versioned single-active profile in the capacity documentation. ## Trigger Start this work when a valid 30-day peak cannot be served with 50% headroom, sustained CPU/memory/state depth crosses the documented thresholds, or product targets exceed the measured envelope. ## Outcome Measure the real bottleneck, select vertical or horizontal scaling from evidence, and publish a new versioned capacity/topology claim. ## Acceptance criteria - Production traffic shape and bottleneck evidence are captured without endpoint/player retention. - New state, limiter, queue, and latency budgets fail closed under overload. - At least 150% of the intended peak passes endurance, failure, recovery, and rollback gates. - Any horizontal design proves deterministic mediator routing and shared-state safety. - The prior envelope remains documented and no unmeasured capacity claim is published.

Kyuubi referenced this issue

2026-07-16 22:40:30 +02:00

Run the real-network canary and declare Rendezvous v1 production-ready #23

Kyuubi referenced this issue

2026-08-22 23:30:09 +02:00

Establish capacity, soak, resilience, and availability topology gates #18

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: HeiKyu/Rendezvous#29