How gabr4ca/webf88 works
Project type and purpose
• This is a full-stack web application for a food ordering system.
• There are two React front-end clients:
• “frontend” for customers placing orders
• “admin” for staff to manage menu items, orders, and users
• The backend is implemented as a set of Node.js services behind an API gateway, each service handling one domain (users, food items, carts, orders).
• MongoDB is the database for all services.
File structure
• Top-level:
• “frontend”: React/Vite SPA for customers
• “admin”: React/Vite SPA for administrators
• “backend”: contains an “api-gateway”, a legacy “backup-monolith”, plus four microservices under “services” (cart, food, order, user).
• “Mongo/playground…”: local MongoDB scripts
• Each microservice has its own package.json, config/db.js, models, controllers, routes, and auth middleware. They connect to MongoDB (likely separate DB or separate collections).
• The API gateway (backend/api-gateway/server.js) routes client requests to the appropriate microservice.
• There are shell scripts (start.sh, lol.sh) for starting services.
README for additional insights
• You infer the stack: React + Vite, Node.js + Express, MongoDB, JWT/OAuth middleware.
Elements
• API layer in another (e.g., dark grey)
• Microservices in green
• Database in orange
• Rectangles for services/servers