How chickensoup269/zero_movie works
Main system components
a. Frontend (Next.js)
• Public user UI (movie listings, seat-picker, 3D-view)
• Admin UI (cinema/dashboard management)
b. Backend (Node.js + Express + TypeScript)
• API layer: routes & controllers
• Business logic: services
• Data access: Mongoose models
• Middlewares: auth, file-upload (multer), cron utilities
c. Database
• MongoDB cluster
d. File storage
• Local “uploads” folder (for images, receipts, etc.)
e. External services
• TMDB API (movie metadata)
• PayPal API (payment processing)
• EmailJS (notifications)
• Gemini AI API (chat/FAQs)
• Python recommendation script (exec’d via child_process)
Relationships & data flows
• User/browser ↔ Next.js frontend (HTTP/HTTPS)
• Frontend ↔ Backend REST/API calls
• Backend controllers → services → models → MongoDB
• Backend calls PayPal API for payments
• Backend calls TMDB API for up-to-date showtimes/genres
• Backend spawns Python process → recommendation engine → returns movie suggestions
• Backend sends emails via EmailJS
• Cron jobs (cronUtils) run background tasks (e.g., session cleanup, data seeding)
• File uploads handled via multer → stored in /uploads → served by backend
Architectural patterns & design principles
• Layered MVC-style separation: routes/controllers → services → data models
• Bounded contexts: Auth, Booking, Cinema, Movie, Payment, etc.
• “Hexagonal”/“Ports & Adapters” style: controllers adapt HTTP to internal services, services adapt to DB or external APIs
• Use of environment variables (.env) to decouple secrets & endpoints
• Frontend follows “app/(admin)” vs “app/(user)” segmentation for role-based routes
Technologies & frameworks to annotate
• Next.js (React + SSR/SSG) + TypeScript + Tailwind CSS + shadcn/ui + Three.js + Framer Motion
• Express.js + TypeScript + Mongoose
• MongoDB
• Python 3.x (recommendation script)
• External REST APIs: PayPal, TMDB, Gemini AI, EmailJS