How phongpahmm/movieticket works
Project Type and Purpose
• This is a backend monolithic web service built with Spring Boot, providing RESTful HTTP and WebSocket APIs for a movie ticket booking system.
• It handles user authentication/authorization, movie/show management, seat booking, payment processing, real-time chat/seat updates, email notifications, and media uploads.
• The project exposes its functionality to a separate frontend (web or mobile) accessible at https://movie-ticket-booking.site/.
File Structure Analysis
• Top-level files: pom.xml, README.md, Maven wrapper → a Maven-based Java project.
• src/main/java/com/example/movieticket:
• configuration: security (JWT filters, handlers), WebSocket, cloudinary, payment, mail.
• controller: HTTP endpoints by resource (Authentication, Movie, Booking, Chat, etc.).
• dto: request/response objects for each API.
• service & service/impl: business logic.
• repository: Spring Data JPA interfaces.
• model: JPA @Entity domain objects.
• common/util: enums and utilities (JWT, pagination).
• exception: centralized error handling.
• src/main/resources: application-prod.yml for env configuration, static assets (faqs.xlsx) and uploaded media in /uploads.
• WebSocketConfig indicates real-time messaging; CloudinaryConfig and VNPayConfig point to third-party integrations.
README Insights
• Only deployment link is provided, but the wide array of controllers and services shows a standard layered architecture.