How thanhhangdang/ltnc works
Main Components
a. Frontend (Client) – Represent the LTNCfe folder:
• That this is a React-based client application.
• UI components such as login, admin dashboard, student and teacher interfaces.
• Directories like “public” and “src/components” to represent the different pages and features.
b. Backend (Server) – Represent the LTNCbe folder:
• Entry point (server.js) and router.js which handles API endpoints.
• Configuration modules (corsConfig.js, databaseConfig.js) to show how cross-origin and database settings are managed.
• Mention that the backend uses Node.js and integrates with MySQL (as suggested by the SQL database files).
c. Database:
• MySQL database system.
• “database.sql” file is used for setting up the schema and data.
Architectural Patterns and Design Principles
• Separation between presentation (frontend) and business logic/data access (backend).
• Although it is not explicitly microservices, the division into LTNCfe and LTNCbe signifies at least a two-tier architecture.
• Use of RESTful APIs if applicable (suggested by the routing file).
• You might also mention any common patterns used in React-based applications (component-based structure) and Node.js server setups.
Relevant Technologies, Frameworks, and Libraries
• Frontend: React, possibly create-react-app (inferred from project structure), with separate components for different roles (admin, student, teacher).
• Backend: Node.js and Express (assumed since server.js and router.js are present), with modules for CORS and database configuration.
• Database: MySQL (using the provided SQL file for database schema).
• Other: npm for dependency management (as seen from package.json files in both LTNCbe and LTNCfe).