Back to Projects
Tiketfy
Engineering

Tiketfy

Full-Stack Developer

NestJSNext.jsPrismaPostgreSQLRedisBullMQPaystackSocket.io

About the Project

Tiketfy is a live event ticketing platform, now running on the NestJS + Next.js architecture I migrated it to from a legacy Vite/Supabase stack. It handles event discovery and management, ticket sales with Paystack payment processing, background job queues, and WebSocket-based real-time notifications, with a separate organiser experience alongside the public site and a dedicated admin console. The migration ran as a rebuild beside the running product rather than a rewrite in place: the two legacy apps still sit in the repo as reference while the new three-app architecture took over.

What It's Made Of

API

NestJS 11 · Prisma 6 · PostgreSQL · Redis

The backend the whole platform now runs on: events and ticket types, orders and Paystack payment callbacks, atomic ticket counting with a reservation path so concurrent buyers cannot oversell a tier, role-seeded RBAC across super-admin, admin, organiser and attendee, BullMQ queues for email and webhooks, and a Socket.io gateway for live notifications. It publishes an OpenAPI spec as a build artifact so both frontends generate against the same contract.

Customer & organiser app

Next.js 16 · Tailwind v4 · shadcn

Two audiences in one app: attendees browsing and buying tickets, and organisers running their own events — creating events and ticket tiers, tracking sales, importing guest lists in bulk, and checking attendees in at the door, which has to stay fast and forgiving on a phone with poor signal at a venue entrance.

Admin console

Next.js 16 · Tailwind v4 · Radix

Platform-level operations separate from the organiser view: approving and moderating events, managing organisers and users, reviewing payments and refunds, and platform-wide reporting. Split out so an organiser's permissions and a platform administrator's are never the same code path.

Legacy apps (superseded)

Vite · React · Supabase

The original customer app and admin dashboard, kept in the repository as reference rather than deleted. They are the stack the platform was migrated off, and the reason the new architecture is three separate apps against one API instead of a frontend talking directly to a hosted database.

Key Highlights

  • Migrated the platform off a legacy Vite/Supabase stack onto NestJS + Next.js without downtime, rebuilding alongside the running product rather than in place
  • Built RBAC with seeded roles and granular permissions separating platform administrators from event organisers
  • Integrated Paystack for payment processing, with order state driven by verified callbacks rather than client-reported success
  • Implemented atomic ticket counting with a reservation queue and database-level locks so concurrent purchases cannot oversell a tier
  • Shipped bulk guest import and bulk check-in for the door, designed for a phone on a bad connection at a venue entrance
  • Implemented real-time notifications over Socket.io, with BullMQ handling email and webhook delivery off the request path

Technical Challenges

Migrating a live platform to a completely new architecture while maintaining service continuity required careful parallel development — the new apps were built and cut over beside the old ones, which is why both legacy apps still sit in the repository rather than having been deleted mid-flight. The atomic ticket counting system was the part that had to be right: database-level locks plus a reservation queue to handle concurrent purchases without race conditions, because overselling a tier is not a bug you can apologise your way out of once people are at the door.