How saketkharche/movie-review-dotnet-project works
• A Next.js/React frontend (moviemo-frontend)
• An ASP.NET Core backend (Moviemo) exposing RESTful endpoints
• A SQL Server database via Entity Framework Core
• (Optionally) Third-party movie info APIs (e.g. TMDB/OMDB)
Main Components
• Frontend: Next.js application (TypeScript + React) located under moviemo-frontend/app
• Pages, components, client-side routing
• api.ts service layer wrapping fetch calls
• Backend API: ASP.NET Core MVC project (Moviemo/)
• Controllers (CommentsController, MoviesController, UsersController, etc.)
• Services layer (IMovieService, ICommentService, ... + implementations)
• Data access via AppDbContext (Entity Framework Core)
• DTOs for request/response contracts
• Database: SQL Server
• Tables for Users, Movies, Reviews, Comments, Votes, Reports, Feedback, RefreshTokens
• Migrations folder showing schema evolution
• External Services (optional):
• Third-party movie data provider (used by frontend or backend)
Relationships & Data Flows
• UI Flow:
User → Next.js UI (pages/components) → HTTP calls to ASP.NET Core API
• Backend Flow:
Controller endpoint receives HTTP request → maps to DTO → calls Service layer → Service performs business logic → uses AppDbContext to query/update SQL DB → returns DTO → Controller returns JSON → Frontend consumes JSON
• Database interactions:
AppDbContext ↔ SQL Server (migrations manage schema)
• Optional:
Backend or Frontend ↔ External Movie API (e.g. for search or details)
Architectural Patterns & Principles
• Layered Architecture (Presentation → API Controllers → Services → Data Access)
• Dependency Injection (Services injected into Controllers, DbContext injected into Services)
• Separation of Concerns (Controllers only handle HTTP, Services encapsulate logic, DbContext handles persistence)
• DTO Pattern (separating domain models from API contracts)
• Next.js Hybrid Rendering (SSR/SSG for pages, client-side navigation)
Technologies & Frameworks to Call Out
• Frontend: Next.js, React, TypeScript, CSS/Bootstrap, fetch (wrapped by moviemo-frontend/app/services/api.ts)
• Backend: .NET 6+, ASP.NET Core MVC, Entity Framework Core, C#
• Database: SQL Server (MSSQL), EF Core Migrations
• Dockerfile (optional containerization)
• LaunchSettings / appsettings.json for environment configuration
Putting It All Together
4. Inside ASP.NET Core API, nest:
• Controllers layer
• Services layer
• Data layer (AppDbContext)