Queue control for high-demand ticketing
Access control under high concurrency.
I implemented a queue layer to stabilize ticket sales under peaks of 10,000+ concurrent users.
Hernán Bonavota
I design and operate platforms where concurrency, validation, and reliability affect sales, access, and operational flows.
Selected work
Queue control, member validation, and registration under concurrency.
Access control under high concurrency.
I implemented a queue layer to stabilize ticket sales under peaks of 10,000+ concurrent users.
Validation flows integrated with LALIGA and Data Lake.
Normalized legacy data and enforced validation at entry points to prevent inconsistencies across systems.
Traffic spikes, duplicate prevention, and data integrity.
Designed registration flows capable of handling high concurrency, duplicate prevention, and consistent data writes in production.
Scope
Where the work usually lives.
Sale flows, access control and member account journeys anchored to the club's operating reality.
Two LALIGA internal platforms — ticketing and member management — integrated through APIs I built and own, plus legacy normalization and validated forms that feed a CRM Data Lake in real time.
Custom plugins, WooCommerce flows and frontend integrations where the business team needs to operate the portal without a deploy.
EC2 (AMIs, scaling), RDS, S3, ACM and Nginx — from staging to release without waiting on a platform team.
Currently
Ticketing, member portals and AWS-backed integrations.
Rezolve
At Rezolve I run ticketing, member portals and LALIGA integrations for professional football clubs. Two LALIGA internal platforms — ticketing and member management — are integrated through APIs I built and operate.
Contact
LinkedIn for roles and tech conversations. GitHub for code.