How phuchau0310/movie-ticket-system works
Project Type and Purpose
• This is a full-stack desktop application:
• MovieTicketAPI (FastAPI-based REST backend)
• MovieTicketApp (C# Windows Forms frontend)
• Purpose: allow Admin/Staff/Customer to manage movies, book tickets (with VNPay), view recommendations (via Pinecone), and track purchase history.
File Structure
• Backend folder (MovieTicketAPI):
• app/main.py: entry point (uvicorn)
• app/routers/*.py: REST endpoints (movies, tickets, users, purchase_history, recommendations)
• app/models.py + database.py: SQLAlchemy models & DB session
• app/schemas.py: Pydantic request/response models
• app/utils: helper modules (vector_utils → Pinecone; vnpay_utils → payment integration)
• alembic/: DB migrations
• Dockerfile + docker-compose.yml: containerization
• Frontend folder (MovieTicketApp):
• Forms/: UI screens by role (AdminForm, AuthForm, CustomerForm)
• Models/: local data models mirroring API schemas
• Services/: ApiClient.cs + domain services (MovieService, TicketService, PaymentService, UserService)
• Utils/Config.cs: configuration (API base URL, keys)
Extract Key Architectural Insights from README
• Role-based access control
• Transactions: VNPay integration
• Recommendations: Pinecone vector similarity
• PostgreSQL as primary datastore
• Docker support for backend
Main Components
a. Frontend Desktop App
• UI Layer (Windows Forms)
• Client Service Layer (ApiClient + domain services)
b. Backend API
• FastAPI Application
• Router Layer (controllers)
• Service/Utility Layer (vector_utils, vnpay_utils)
• Data Access Layer (SQLAlchemy models + Alembic)
c. Database
• PostgreSQL instance
d. External Services
• Pinecone Vector DB
• VNPay Payment Gateway
e. Infrastructure
Relationships and Data Flows
• Desktop App → HTTP requests → FastAPI routers
• Auth (login/register)
• Movie CRUD (Admin)
• Ticket booking → vnpay_utils → VNPay
• Recommendation requests → vector_utils → Pinecone
• Purchase history retrieval
• FastAPI → SQLAlchemy → PostgreSQL
• Alembic applies migrations to PostgreSQL
• Optional: show Swagger UI for API docs
Architectural Patterns & Principles
• Layered architecture (Presentation → Controllers/Routers → Business Logic/Utils → Data Access)
• Separation of concerns: UI vs. networking vs. business logic
• Dependency injection for DB session in routers (via FastAPI)
• Externalized configuration (Docker, .env)
Essential Elements Checklist
• Frontend → Backend
• Backend → DB
• Backend → Pinecone / VNPay
• Container boundary for Docker if drawing deployment view