How alandeabhijeet/course works
Main Components
• Frontend Client: Built using React.js and Tailwind CSS.
• Auth Microservice (backend/auth): Handles user registration, login, token management (JWT), and user-related operations such as verifying course ownership or purchase.
• Course Microservice (backend/course): Manages course creation, listing, editing, deletion, and retrieval of courses based on ownership or purchase.
• Database: A central MongoDB Atlas instance that both backend services connect to via Mongoose.
Separate the Backend Microservices
• Since the instruction specifies “backend also separate please”, explicitly represent the Auth and Course microservices as distinct components.
• That each microservice has its own internal structure including its respective routes, controllers, models, and configuration files.
Relationships and Interactions
• That both Auth and Course microservices communicate with the central MongoDB Atlas database.
Architectural Patterns and Design Principles
• RESTful API Communication: Clearly mark the use of REST endpoints.
• Separation of Concerns: Emphasize that authentication and course management functionalities are handled by dedicated services.
• Common middleware practices in the Auth service (e.g., JWT-based token validation) as part of its architectural design.
Technologies and Dependencies
• For the Auth Microservice: Note the use of Node.js, Express.js, JWT for authentication, and Mongoose for MongoDB interactions.
• For the Course Microservice: Highlight the use of Node.js, Express.js, and Mongoose.
• For the Frontend: Specify React.js and Tailwind CSS.
• Database: Represent MongoDB Atlas as the persistent data store for both services.