Stone Watch Party Case Study — Jedidiah Amaraegbu

web · front-end · back-end

Started Jul 2026

My role Full-stack development and registration workflows

Public event page and registration flow

TypeScript · React.js · Next.js · TailwindCSS · PostgreSQL · Redis · Vercel · Docker · Playwright · Drizzle · Auth.js · Zod · Git

Stone Watch Party was built for a World Cup final screening with a 750-seat venue. The site gives guests a mobile-friendly route from event details to registration while supporting seat allocation behind the scenes.

Hardest challenge

Two guests can try to claim the same remaining seat at once. The booking service has to enforce capacity at the data boundary, while the public availability display stays clear and current enough to guide registration.

What I built

Event landing and registration flow
Seat allocation and event data modeled with PostgreSQL and Drizzle
Validation and authenticated administration for managing registrations

Lessons learned

The availability shown in a browser cannot be the final authority for a booking. Database-backed allocation and concurrency tests were needed to protect the seat count when requests arrive together.

Why I chose Drizzle for this, and how the last-seat claim works in code: Prisma vs. Drizzle: Why I Reach for the Lighter ORM.

Evidence and status

Event site - built around a 750-seat venue. The source includes database integration tests for concurrent seat allocation and registration throttling.