How hakanlsk/blog-app works
Project Type and Purpose
• Full-stack web application built on the MERN stack (MongoDB, Express, React, Node.js).
• Purpose: Provide authenticated users the ability to register, log in, create/read/update/delete blog posts, and manage their profile.
Main Components
a. Frontend (client/)
– React application (UI layer)
– Routes/pages: Login/Register, Home (post feed), Create/Edit Post, Profile
– State management (local state or context)
– Communication: HTTP calls (fetch or axios) to backend API
b. Backend (server/)
– Node.js + Express server (server/server.js)
– Routes layer (server/routes/*.js)
– Controllers (server/controllers/*.js)
– Helpers (e.g., authHelper.js for JWT operations)
– Models (Mongoose schemas in server/models/*.js)
c. Database
– MongoDB (configured via server/config/db.js, using MONGO_URL from .env)
d. External/Infrastructure Services
– Environment variables (.env via dotenv)
– CORS (cross-origin requests)
– Logging (morgan)
– JWT service for authentication
– bcrypt for password hashing
Architectural Patterns & Design Principles
• MVC-ish layering on the backend:
– Models ↔ Controllers ↔ Routes
• Stateless REST API:
– Endpoints protected by JWT middleware (authHelper)
• Separation of concerns:
– Frontend UI isolated from backend API
– Environment/config isolated via dotenv files
• CRUD operations for posts and users
Component Relationships & Data Flow
1. User interacts with React UI → triggers API call (HTTP request) →
2. Express route (postRoutes/userRoutes) →
3. Controller (postController/userController) →
4. Model (Mongoose) →
5. MongoDB read/write →
6. Controller responds →
7. Frontend updates state/UI
• Authentication flow:
– Login/Register requests → controller hashes password or compares → on success, generate JWT → send token to client → client stores (localStorage) → attach token to subsequent API calls (Authorization header)
• Clear component labels
• Grouping of related modules (e.g., server/controllers, server/models)
• External dependencies (MongoDB Atlas or self-hosted, JWT issuer, bcrypt)