Ticketing Queue Control
Concurrency control for high-demand sales windows.
Queue-Fair integration for ticketing launches that were collapsing under roughly 10,000 concurrent users.
Role
Software Engineer / Technical Owner
Type
Client Project
Context
Context
This work sat inside ticketing portals for professional football clubs running high-demand sales windows. Before the change there was no queue system, so users entered the sale flow at the same time and the portal broke under load.
Problem
Problem and constraints
The immediate problem was uncontrolled concurrency: timeouts, failed purchases and lost revenue once traffic reached roughly 10,000 concurrent users.
A key constraint was the external AVET system from LALIGA. It was a hard dependency in the flow and it did not scale under peak traffic, so the practical solution had to regulate access before users reached that point.
The issue was already affecting the business side. One account had been lost after the platform failed during this kind of launch.
Approach
Approach and technical decisions
I evaluated queue providers and selected Queue-Fair based on cost, fairness in the waiting room and evidence of use at higher scale.
I handled the vendor conversation and agreement directly in English, then implemented Queue-Fair through a frontend script on WordPress because it gave faster rollout, simpler maintenance and direct operational control.
The implementation combined that script integration with a decoupled match landing page, so access control could be activated and adjusted from WordPress without backend changes.
Challenges
Challenges
Outcome
Outcome
The sale flow stopped collapsing at around 10,000 concurrent users and moved to an ordered waiting room of roughly 60,000 users.
That gave the ticketing operation a controlled entry point and supported larger commercial accounts afterwards.