Enterprise room booking platform with real-time status, conflict detection, and analytics dashboard
17 weeks
7
Production
Key Challenge
Atomic conflict detection on booking creation without race conditions under concurrent requests
Skills Demonstrated
Built an internship project delivering room CRUD, booking conflict detection, dashboard analytics, and a modern Next.js frontend connected to a NestJS + Prisma + PostgreSQL API.
Manual room booking led to double-bookings and no visibility into room availability
Automated conflict detection with real-time dashboard and room state machine
Centralized booking system with analytics for Al Baraka meeting rooms
<250ms
Dashboard load
100%
Conflict detection accuracy
4
Room states
3
Booking statuses
6+
Dashboard metrics
Screenshot 1
Delivered a working room management system for Al Baraka internship.
Eliminated manual booking conflicts and provided real-time room visibility.
42
Commits
17
Weeks duration
Decoupled frontend-backend architecture. Next.js 14 frontend on port 3001 communicates with NestJS API on port 3000 via typed fetch client.
Prisma manages PostgreSQL with Room and Booking models. Service layer validates time ranges and checks overlaps before persisting.
React Context provides global filter and UI state; custom hooks wrap API calls with loading/error handling.
Infrastructure & Deployment
Frontend deployable on Vercel; backend on Render or Docker container with PostgreSQL.
CRUD for rooms with capacity, floor, and status.
Create bookings with automatic conflict detection.
Real-time stats on room utilization and today's bookings.
Filter by floor, status, and capacity.
Visual timeline of room reservations.
Employee profile and booking history.
The Problem
Two users booking the same room for overlapping times caused conflicts.
How I Solved It
Service-layer query checking active bookings with overlapping time ranges before insert.
const conflict = await prisma.booking.findFirst({
where: { roomId, status: 'ACTIVE',
startTime: { lt: endTime }, endTime: { gt: startTime } },
});
if (conflict) throw new ConflictException('Room already booked');The Problem
Users could create bookings in the past.
How I Solved It
Validation pipe rejects startTime before current timestamp.
if (dto.startTime < new Date()) throw new BadRequestException('Cannot book in the past');The Problem
API errors crashed components without user feedback.
How I Solved It
ErrorBoundary wrapper and ErrorAlert component with retry logic in useApi hook.
Conflict checks belong in the service layer
Database constraints help, but explicit overlap logic in the booking service gives clear error messages to users.
Room state is separate from bookings
MAINTENANCE state should block bookings regardless of calendar availability.
Internship scope needs clear MVP
Focused on dashboard + booking first; profile routes were cut to ship on time.
What I'd Do Differently
Add WebSocket push for live room status instead of polling, and implement role-based access for admins vs employees.
School project management API with layered security, email verification, and workshop tracking.
Next.js 16 portfolio platform with Prisma, admin CRUD, EN/FR i18n, quote calculator, and cached public getters.
Interested in a project like this or want to collaborate on your own?