How sachinggsingh/vichar_manthan works
Project Type and Purpose
• Full-stack web application (MVC pattern).
• Purpose: Users can sign up/in, create, edit, view, and delete blog posts. Images and static assets are served from a public directory.
File Structure
• Top-level files:
• app.js – Express app entry point
• .env – environment variables
• Directories:
• routes/ – Express routes (blog.js, user.js)
• controller/ – route handlers (userCTRL.js)
• services/ – business logic/auth (auth.js)
• middleware/ – request guards (authentication.js)
• models/ – Mongoose schemas (blog.js, user.js)
• views/ – EJS templates (pages & partials)
• public/ – static assets (CSS, images, uploads)
Key Architectural Patterns & Components
• MVC layers:
• View layer: EJS templates
• Controller layer: routes → controller functions
• Model layer: Mongoose models
• Layered services: authentication logic separated into services and middleware.
• Monolithic Express server hosting both static and dynamic content.
• MongoDB as the primary datastore (could be a replica set or Atlas).
• File uploads stored in public/uploads (no separate file-storage service).
Main Components
a. Client Browser
• Sends HTTP(S) requests, receives HTML/CSS/JS.
b. Reverse Proxy / Load Balancer (optional)
c. Express.js Server
• app.js: configures middleware, routes, view engine.
• Middleware: authentication.js
• Routes: user.js, blog.js
• Controllers: userCTRL.js
• Services: auth.js
• Models: user.js, blog.js
d. MongoDB Cluster
• Collections: users, blogs
e. Static File Store
• public/ folder (images, CSS, site manifest, uploaded files)
f. Optional External Services
• Email service for notifications
• Cloud storage (if migrating uploads off-premise)
Interactions & Data Flows
1. Client → (1) HTTP GET / POST → Express server
2. Express → authentication middleware → controller
3. Controller → service layer → model/DB
4. DB → returns data → model → service → controller
5. Controller → renders EJS view or returns JSON
6. Public assets served directly from Express (static middleware)
7. Uploads: controller writes to public/uploads
Final Checklist
• All components clearly labeled.
• Static content path separated from dynamic routes.
• Optional scaling components (load balancer, CDN for static assets, replica set for MongoDB).