How roy7077/e-commerce-website works
Project Type and Purpose
• Full-stack e-commerce web application using the MERN stack.
• Key features: user authentication, product search, cart/orders, payment processing (Razorpay), refunds.
File Structure
• Top-level:
• client/ – React.js front end
• server/ – Node.js + Express.js back end
• client/src/Components – individual React UI components (NavBar, Cart, ProductCard, etc.)
• client/src/utils – Redux Toolkit slices (Cartslice.js) and store setup
• server/Config – MongoDB and Razorpay config
• server/Controllers – business logic for Authz, Ecommerce, Razorpay
• server/Middlewares – authentication middleware
• server/Models – Mongoose schemas (User, Cart, Payment, OrderedProducts)
• server/Routes – Express routes (paymentRoutes.js)
• server/index.js – entry point tying everything together
README for Insights
• Tech stack and external dependencies (MongoDB, JWT, Razorpay)
• API endpoints grouped by domain (Auth, Cart, Payment, Orders)
Main Components & Their Relationships
A. Client Browser
• React App (client/src)
• UI Components
• Redux Store (Cartslice)
B. API Server
• Express.js App (server/index.js)
• Routes (/api/v1/…)
• Controllers (Authz, Ecommerce, Razorpay)
• Middleware (Authz)
• Config (databases.js, razorpay.js)
C. Data Layer
• MongoDB (Users, Carts, Payments, OrderedProducts)
D. External Service
• Razorpay API
Interactions:
1. User → React UI → Redux store/state → HTTP requests to API
2. Express Routes → Authz Middleware (JWT) → Controllers
3. Controllers ↔ Mongoose Models → MongoDB
4. Payment flows: Controller ↔ Razorpay API
5. Controller returns data → Express Response → React UI updates
Architectural Patterns & Design Principles
• “Container” separation: UI vs API vs Database vs External Service
• MVC-style on the backend:
• Routes = Controllers’ entrypoints
• Controllers = Business logic
• Models = Data layer
• Frontend component hierarchy + Redux for state management
• JWT-based authentication middleware protecting routes
• Separation of configuration (database credentials, Razorpay keys) via Config files and environment variables (.env)
Elements
• Labels for each container/component (e.g., “React App”, “Express API”, “MongoDB”, “Razorpay”).
• Blue for client components
• Green for server components
• Orange for database
• Purple for external services
• Routes layer calls → Authz Middleware → AuthzController or EcommerceController or RazorpayController
• Controllers invoke → Mongoose Models → perform DB operations
• RazorpayController uses → Razorpay config (key id/secret) → External API