TicketAdda
A high-traffic event ticketing platform that sold 15,000+ tickets over a single 5-day live event.
- 15,000+
- tickets sold
- 5 days
- live event
- 01Payment succeeds
- 02Ticket generation fails
- 03Cron (every 2 min) finds paid + pending
- 04Retry generation
- 05Ticket sent → status updated
— Problem
Booking and availability had to hold up under many simultaneous purchases during one live event, with the frontend never able to control ticket status directly.
— What I built
I built the booking and availability logic server-side, plus a 2-minute cron job that catches one nasty failure mode: payment succeeds, but a network blip stops the ticket from generating. The job finds paid orders with a pending ticket and retries; once sent, the status flips so nothing is duplicated. An admin override covers the rare case where retries still fail.
— My role
I built this solo, end to end: frontend, backend, database, booking flow, payment integration, ticket generation and deployment. I monitored and supported it in real time during the event.
→ Result
Handled 15,000+ sales across the event. The retry system recovered ticket-generation failures after successful payments automatically, so temporary network issues didn’t mean generating every affected ticket by hand.
- React
- Node.js
- Express.js
- MongoDB
- REST APIs
- Payment gateway



























