01 / 04 · Zentix
Concert tickets, from queue to gate
A ticketing platform for concerts and campus events, live in production with real people buying tickets. Event listings, checkout and e-tickets all run on its backend.

The problem
My campus wanted its own ticketing system for its concerts, rather than handing ticket sales to a third-party app. So our team of students was asked to build one.
What I built
I own the backend, built in Python with FastAPI on MySQL: the API for accounts, events, ticket orders and payments that the rest of the team builds on.
How it works
A buyer picks a ticket and checks out. The backend creates the payment through iPaymu, the payment gateway, and sends back a QR code to pay with.
When a concert goes on sale, everyone arrives at once. A rate limiter keeps that rush from overwhelming the API, and so far it has held up.
Each online ticket is later exchanged for a wristband, and there are only so many wristbands. So online sales stop while a few tickets are still in stock, a buffer the organisers can set from the admin panel, and a last-second rush can never sell more tickets than there are wristbands.
On the day, the committee scans each online ticket and exchanges it for a wristband at the gate.
What came of it
More than 8,000 people have signed up so far.
For me, it was where the real journey started. Campus had taught me the basics, but never a real project. Zentix taught me how a system people actually use is built and kept running, and gave me the nerve to take on the real projects that came after it: Tiss Valley, the LMS and the IDC website.