sujith123143/movie-application

Purpose and entry points

This is a MERN movie-management and viewing application: a React/Vite client consumes an Express API for movies, genres, users, authentication, and uploads. Backend startup is backend/index.js; frontend bootstrap and application composition are frontend/src/main.jsx and frontend/src/App.jsx.

Backend HTTP layer

Express routes divide the API by domain: movies, genres, users, and uploads in backend/routes/moviesRoutes.js, backend/routes/genreRoutes.js, backend/routes/userRoutes.js, and backend/routes/uploadRoutes.js. These route modules are the principal boundary between the SPA and server-side application logic.

Controllers and request pipeline

Domain controllers implement API operations and coordinate persistence: backend/controllers/movieController.js, backend/controllers/genreController.js, and backend/controllers/userController.js. Shared middleware handles asynchronous controller failures, identity validation, and authorization before controllers execute: backend/middlewares/asyncHandler.js, backend/middlewares/checkId.js, and backend/middlewares/authMiddleware.js.

Persistence and authentication

MongoDB is the persistence runtime, initialized through backend/config/db.js. Mongoose-style domain records define the core data model in backend/models/Movie.js, backend/models/Genre.js, and backend/models/User.js. Authentication tokens are created in backend/utils/createToken.js and enforced at protected-route boundaries by backend/middlewares/authMiddleware.js.

Client state and API integration

The React client uses Redux Toolkit state plus an API layer. Store assembly is in frontend/src/redux/store.js; authentication state is maintained by frontend/src/redux/features/auth/authSlice.js; movie-specific local state is in frontend/src/redux/features/movies/moviesSlice.js. API endpoints are centralized through frontend/src/redux/api/apiSlice.js and domain endpoint modules such as frontend/src/redux/api/movies.js, frontend/src/redux/api/genre.js, and frontend/src/redux/api/users.js.

User-facing movie flows

Movie discovery, listing, cards, details, and related viewing UI are organized under frontend/src/pages/Movies/AllMovies.jsx, frontend/src/pages/Movies/MovieDetails.jsx, and frontend/src/pages/Movies/MovieTabs.jsx. These views fetch movie/genre/user data through the Redux API layer rather than directly owning backend logic.

Identity and administration boundaries

Authentication screens and client-side protected navigation reside in frontend/src/pages/Auth/Login.jsx, frontend/src/pages/Auth/Register.jsx, and frontend/src/pages/Auth/PrivateRoute.jsx. Administrative workflows—movie creation/editing, genre management, comment review, and dashboard presentation—are separated under frontend/src/pages/Admin/CreateMovie.jsx, frontend/src/pages/Admin/UpdateMovie.jsx, and frontend/src/pages/Admin/Dashboard/AdminDashboard.jsx. Client guards complement, but do not replace, backend token middleware.

Runtime and delivery shape

The frontend is a Vite React application (frontend/vite.config.js, frontend/package.json) styled with Tailwind configuration (frontend/tailwind.config.js). The backend is Node.js/Express with environment-driven settings in .env; it connects to MongoDB and exposes the API consumed by the independently built frontend.