Status: Analyzing
Due: Sep 25, 2027
Assignees: Pak Youngjae
Risk statement. The auth service was built for 5,000 concurrent sessions. Launch modelling projects a peak of 22,000. It has never been load-tested above 8,000, and the session store is a single unreplicated instance.
Trigger / early warning. Load test failing above 12,000 concurrent sessions, or p99 login latency exceeding 800ms in staging.
Consequence if realised. Users cannot log in on launch day. This is the most visible possible failure and the one hardest to explain afterwards.
Current response. Mitigate. Load test to 25,000, replicate the session store, and put a queue-based throttle in front as a last resort.
Risk ID:
Date Identified: Jul 28, 2027
Likelihood: 4 · Likely
Impact: 4 · Major
Response Strategy: Mitigate
Risk Score: 16
Category: Technical & Quality
Risk Level: Critical (15-25)
R-10
Date Identified: Jul 28, 2027
Likelihood: 4 · Likely
Impact: 4 · Major
Response Strategy: Mitigate
Risk Score: 16
Category: Technical & Quality
Risk Level: Critical (15-25)
Created by Vicky Aug 7, 2026, Edited Aug 7, 2026