01 / Project case study / 2025
DevEvent
Connected event platform
A connected path from discovering a developer event to booking a place, receiving a QR ticket and checking in.
Explore the problem. Follow the system.
02 / The problem
A reason to build.
Event discovery and attendee management often happen in different tools. Organizers need one flow for publishing events, handling bookings and verifying attendance; visitors need searchable events and an accessible ticket.
03 / System design
Follow the architecture.
A pnpm monorepo separates the Next.js 16 frontend from a NestJS API. MongoDB stores events, users and bookings; MinIO handles media storage. API queries support search, tags, filters and pagination. Booking services generate QR tickets, validate their event and attendee data, and record check-in. GitHub Actions builds Docker images for deployment, with Railway configuration also maintained in the repository.
- 01Discover
- 02Search + filter
- 03Select event
- 04Book
- 05QR ticket
- 06Check in
04 / Engineering decisions
The choices inside.
- 01
Keep frontend and backend in separate packages with a shared deployment workflow.
- 02
Store event media separately from event and booking documents.
- 03
Validate ticket data against the event and booking before recording attendance.
05 / Technology
A stack with purpose.
The technologies connecting this system.
- Next.js
- React
- TypeScript
- NestJS
- MongoDB
- MinIO
- QR codes
- Docker
- GitHub Actions
06 / Engineering outcome
Architecture, applied.
Connects discovery, event management, bookings and attendee check-in in one product. Organizers can review participants and export booking records, while attendees can retrieve their QR tickets.