Build log/Events

Building event software that survives on-sale day

Most event platforms are quiet for weeks, then face their busiest minute of the year. Here is how to build ticketing and check-in that hold up.

The short answer

  • Put a waiting room in front of checkout, so buyers are let through at a pace the system can handle.
  • Hold tickets for a few minutes while people pay, and make sure a retried payment can never charge twice.
  • Download the guest list to scanners before doors open, so check-in keeps working when the venue Wi-Fi doesn’t.

The busiest minute of the year

An event platform can sit quietly for weeks, then face tens of thousands of people in the minute tickets go on sale. Systems sized for an average day fall over, checkout slows, and buyers refresh the page, which makes it worse.

A waiting room in front of checkout

A virtual waiting room lets everyone in at once to a lightweight page, then releases buyers into checkout at a steady rate. It is fairer, because people are served in order, and it protects the parts of the system that take payments.

Holds, not oversells

When a buyer selects a ticket, it is held for a few minutes while they pay. If they abandon checkout, the hold expires and the ticket goes back on sale. Without holds you either oversell, or lose sales to people who never complete.

Payments that can’t double-charge

Under load, requests time out and get retried. Every payment request carries a unique key, so a retry is recognised as the same payment rather than a new one. Payment providers such as Stripe support this directly.

Test the spike before the date

Load testing with realistic traffic, a few weeks before a big on-sale, shows where the system bends. Static pages and cached content take most of the load off the parts that can’t be cached.

Doors open, Wi-Fi down

Venue Wi-Fi is often overloaded by the very crowd you are trying to check in. Scanners download the guest list before doors open and validate tickets on the device. Scans sync when a connection returns, and a ticket scanned at two entrances while both were offline is flagged as soon as they reconnect.

Planning event software? See what we build for events.
Written by Flavoureak

We build and run Estimark, CurioKids and CalcStack, and we build web and mobile software for other businesses. Start a project.