How iamrajatroy/movys works
Project type and purpose
• This is a full-stack movie recommendation application.
• Frontend: Angular SPA, built under src/main/ui and bundled into the Spring Boot JAR (served via Thymeleaf/static).
• Backend: Spring Boot (Java) REST API under src/main/java/com/codeit/rajat/movys.
• Recommendation microservice: Python Flask app under python_code/movie_recommender, containerized with Docker.
• Data store: in-memory Apache Derby (embedded in Spring Boot).
• Offline data ingestion: Python notebooks under python_code use TMDb API to fetch and clean movie data.
File structure
• Top level:
• pom.xml, .mvn, mvnw: Java build (Maven) for Spring Boot
• src/main/java/...: Spring Boot application, organized by packages (config, component, controller, service, persistence) following MVC + repository pattern
• src/main/resources: Derby CSV under db/, Thymeleaf template index.html, static assets (Angular build output) under static/js, static/css
• src/main/ui: Angular source—modules, components, services—built via package.json scripts into dist and copied into resources/static
• python_code/movie_recommender: Flask recommender service, Dockerfile, docker-compose.yml
• demo: screenshots/GIF for README
README for additional insights
• Describes data flow: user likes movies → Java backend persists in Derby → backend calls recommendation service (Flask in Docker) → Flask returns similar movies → backend responds to Angular UI.
a. Main components
1. Client Browser / User Interface (Angular SPA)
2. Spring Boot Application (Java)
3. Python Flask Recommender Service (Docker container)
4. In-memory Derby Database
5. (Optional) External TMDb API for data ingestion
b. Relationships & interactions
• User ↔ Angular UI (HTTP)
• Angular UI → Spring Boot REST endpoints (/api/movies, /api/recommend)
• Spring Boot → Derby (JDBC repositories) for CRUD on movies and user likes
• Spring Boot → Python Flask service (HTTP over Docker network) to compute recommendations
• (Offline) Python notebooks ↔ TMDb API to fetch raw movie data
c. Architectural patterns & design principles
• MVC on Spring Boot: controllers → services → repositories
• Microservice boundary: content-based recommender isolated in Flask/Docker
• Single-page application served as static assets by Spring Boot + Thymeleaf shell
• Embedded in-memory DB for simplicity and zero-ops persistence
• Docker Compose for orchestrating the Python service
d. Key technologies
• Java / Spring Boot / Spring Data JPA / Apache Derby
• Angular / TypeScript / RxJS
• Python / Flask / scikit-learn (content-based filtering)
• Docker / Docker Compose