How goodviet/e-commercets works
Main components
a. Front-end (Angular SPA)
b. Back-end (Node.js/Express)
c. Database (MongoDB)
d. Admin UI (Express/EJS templates + static assets)
e. Real-time chat micro-service (Socket.IO)
f. Deployment/hosting layers (e.g., Netlify, Heroku/AWS)
Relationships and data flows
• Browser ↔ Angular SPA: HTTP (port 4200 during dev, or served statically via Netlify)
• Angular → REST API: HTTP calls (GET/POST/PUT/DELETE) to Express endpoints under /apis or /router
• Express Controllers → Mongoose Models → MongoDB: database CRUD
• Browser (Admin) ↔ Express/EJS views: server-rendered HTML + static assets served from /public/admin
• Angular Chat Component ↔ Socket.IO Server: WebSocket connections for real-time messaging
Architectural patterns
• Front-end: component‐based module structure, Angular Router, services for HTTP, NgRx‐style store (counter.reducer.ts)
• Back-end: MVC pattern
– Routers (router/*.js)
– Controllers (controllers/*.js)
– Models (models/M_*.js) using Mongoose
• Real-time: dedicated Socket.IO server (could be mounted in Express or run separately)
Incorporate key technologies
• Angular (TypeScript, RxJS, Angular CLI)
• Node.js + Express
• MongoDB (NoSQL) via Mongoose driver
• Socket.IO
• EJS templating for admin
• Netlify (frontend deployment), Node host (backend)
1. Browser/Client
• Angular SPA (components, services, state)
• Chat Component ↔ WebSocket
2. REST API Layer
• Express App (project 2/app.js)
• Routers (router/*.js)
• Controllers (controllers/*.js)
• Services (if any)
3. Admin UI
• EJS Templates (views/admin/*.ejs)
• Static Assets (public/admin/assets)
4. Database
• MongoDB (Collections: Users, Products, Orders, Categories, etc.)
5. Real-time Chat Service
• Socket.IO server (socket-io-angular/server.js)
6. Deployments
• Netlify (serves Angular dist/angular)
• Node Host & MongoDB (Cloud/On-prem)