How harshitpg/mfc-recruitment-portal-be works
Main Components
A. Client Layer
• External clients (Recruitment Portal Frontend)
• Connection through HTTP/REST APIs
B. API Gateway Layer
• Express.js Server
• Rate Limiting Middleware
• Authentication/Authorization Middleware
C. Core Application Layer
• Controllers (Auth, Admin, Task, User, Status)
• Routes
• Middleware
• Utils (Email Services)
D. Data Layer
• MongoDB Database
• Models (User, VerificationModel, DesignTask, TechTask, Management)
Component Relationships
• Client → API Gateway (HTTP/REST)
• API Gateway → Core Application Layer (Internal routing)
• Core Application Layer → Data Layer (Database operations)
• Core Application Layer → External Services (Email service)
Detailed Component Breakdown
• Token Validation
• Admin Validation
• Domain Validation
• File Validation
• Rate Limiting
• Verification Validation
• Auth Controller (User authentication, verification)
• Admin Controller (User management)
• Task Controller (Submission handling)
• User Controller (Profile management)
• Status Controller (Progress tracking)
• User Model
• Verification Model
• Design Task Model
• Tech Task Model
• Management Model
Special Features to Highlight
• Email Verification Flow
• File Upload System
• Domain Selection Process
• Admin Promotion System
• Task Submission Control
Additional Elements
• Security Layer (showing token-based authentication)
• Email Service Integration (NodeMailer)
• File Upload Flow (Multer)
• Domain-specific Task Management
[Client Layer]
• ↓
[API Gateway/Security]
• ↓
[Middleware Layer]
• ↓
[Controllers/Business Logic]
• ↓
[Data Access Layer]
• ↓
[Database]
A side panel showing external services (Email) and utilities.
Important Notes for the Engineer:
• Keep the authentication flow prominent as it's a crucial security feature
• Task submission workflow as it's a core functionality
• Clear separation between admin and user functionalities
• Database relationships between models
• Adding a small zoom-in view of the task submission process as it's a critical feature