An EdTech video-authorization API under exam-night traffic — and which of four scaling plans wins on expected value, risk, and stability.
Every "Watch Lesson" tap fires a Laravel/PHP-FPM API call: token validation, subscription, device session, lesson access, log write, signed-URL generation, response. Nine PM on exam-prep night, all 2,600 hit play within a fifteen-minute window.
k · μ = 40 × 1.82
λ during exam spike
Queue grows without bound
When λ exceeds kμ, mobile clients time out, students retry, and arrivals climb to ~180 req/s. The system enters a retry-storm failure mode.
Computes seven operating characteristics — P₀, Lq, L, Wq, W, Pw, Pn — for each of 4 decisions × 4 traffic states.
Output: which architectures are technically feasible.
Backward-pass expected value across 4 decisions and 4 states; risk profile and EVPI; sensitivity in 3 dimensions.
Output: which feasible option minimizes expected cost.
Anderson §11 · M/M/k multi-channel · the math that decides which servers stay up.