80,000 tickets, one turnstile, zero second chances

Most systems scale on a curve. Stadiums scale like a wall: there is no "gradual traffic increase" when 80,000 people arrive within the same two-hour window, each holding a ticket that must validate at the turnstile in under a second. When it fails, the problem is not a 500 error — it is a crowd piling up at the door.

Legacy is not the villain of this story

At the center of operations like this there is usually a legacy system that has already proven itself selling millions. Rewriting everything would be the classic overexcited-architect mistake. The right move is different: surround the legacy with new services that take over the heavy lifting — batch processing, high-volume communication, integrations — and let the core keep doing what it already does well. That is how hours-long processes started finishing in minutes, without stopping the operation to swap the engine.

A turnstile is a distributed system with legs

Integrating tickets with stadium turnstiles teaches you fast that stadium networks are hostile, hardware has opinions, and fans will not wait for your exponential-backoff retry. The design must assume the worst: fast validation close to the turnstile, resilient synchronization, and the golden rule — the turnstile must never depend on a remote call to spin.

Lessons I carry into any system

• A physical deadline changes everything: kickoff is at 4pm whether you are ready or not. Incomplete features get cut; reliability does not.
• Serverless shines under spiky load: paying per execution makes sense when your traffic is 50 events a year with brutal peaks.
• Modernization is strategy, not aesthetics: the legacy stayed at the center, and that was the right call. Full rewrites are the last option, not the first.
• Hours-long processes become minutes when you stop treating batches as sacred and break the work into parallelizable units.

Live-event systems are the best humility school in engineering: production grades you in front of 80,000 people. Passing that exam a few dozen times changes how you design anything — even a contact form.