An event ticketing platform for 20,000+ registrants

The challenge

A high-profile event needs its registration, ticketing and access control to simply work — no dropped sign-ups, no double-issued tickets, no queues stalling at the door. The hard part isn't the happy path; it's staying reliable at scale, especially on event day when thousands of people register in bursts and hundreds check in within the same short window. The platform had to hold up under that load while keeping the data clean and the door experience smooth.

What I built

• A registration flow that captured registrants reliably and validated their data before it ever reached the database.
• Ticketing that issued and tracked tickets against each registration, keeping every ticket accounted for.
• Access control so only valid ticket holders could be checked in, with fast, dependable verification at the door.
• A GraphQL API on Prisma + PostgreSQL giving the front end a typed, precise contract over a well-modelled relational schema.
• A Next.js front end in TypeScript, tying registration, ticketing and check-in into one coherent, maintainable application.

The result

The platform handled 20,000+ registrants and managed1,500+ attendees through its ticketing and access-control flows. Registration, ticketing and check-in all ran through the same system, so the event had one reliable source of truth for who had signed up and who was actually in the room.

The takeaway

Data-heavy web apps live or die on reliability under real deadlines — an event date doesn't move, so the software has to be right the first time. A typed stack (Next.js, TypeScript, GraphQL, Prisma, PostgreSQL) made that dependability practical: a clean data model and a precise API contract meant fewer surprises when the traffic arrived. If you need a web application built to hold up under real load, see how I approachweb application development, or read about theeducation mobile appI grew past 200,000 downloads.