How saksham2882/mern-food-app works
Project Type and Purpose
• This is a full-stack MERN (MongoDB, Express, React, Node.js) food-ordering application.
• Users browse menus, manage carts, apply coupons, checkout with Stripe, and track orders.
• The backend (Node.js/Express/MongoDB) serves REST APIs; the frontend (React/Vite) consumes them.
High-Level Architecture Overview
• Main Components:
a. Frontend Client (React app)
b. API Server (Express/Node.js)
c. Database (MongoDB via Mongoose)
d. File Storage (local uploads folder for images)
e. External Service (Stripe payment gateway)
• Interaction Flow:
• User clicks in the React UI → Axios calls backend REST endpoints
• Backend authenticates (JWT via auth middleware) → Queries/updates MongoDB
• On payment, backend calls Stripe API → Confirms payment → Updates order status
• Frontend receives responses → Updates UI / StoreContext / React Router routes
Architectural Patterns & Design Principles
• Frontend: Component-based UI + React Router for page navigation + Context API for global state.
• Backend: MVC-style separation
• Models: Mongoose schemas (userModels.js, FoodModels.js, orderModel.js)
• Controllers: Business logic (UserController.js, FoodControllers.js, etc.)
• Routes: Route definitions (userRoutes.js, FoodRoute.js, etc.)
• Middleware: JWT auth (auth.js) and request preprocessing
• RESTful API design with clear resource endpoints (/api/user, /api/food, /api/cart, /api/order).
• Secure authentication using bcrypt (password hashing) + jsonwebtoken (JWT).
• File uploads handled by Multer, stored under /backend/uploads.
• Sub-components: Pages (Home, Cart, PlaceOrder, MyOrders, Verify), Reusable components (Navbar, Footer, FoodItem), Context (StoreContext.jsx)
• Technology: React, Axios, React Router, Context API, CSS, Vite
• Sub-components:
– Server (server.js)
– Config (db.js for MongoDB connection)
– Routes → Controllers → Models
– Middleware (auth)
– File Uploads (Multer → /uploads)
• Technology: Node.js, Express, Mongoose, dotenv, cors
• MongoDB Atlas or local instance
• Collections: users, foods, carts, orders
• External Services
• Stripe API (payment processing)
• Optional: Email/Notification service (if added)
• Deployment
• Frontend: Vercel (via vercel.json)
• Backend: Node host (Heroku, DigitalOcean, etc.)
Detail Level
• Data flow from UI to DB and back is crystal clear.