How amoghphadnis/quickswift works
Project type and purpose
• This is a full-stack web application implementing a multi-role food-delivery/order system.
• The front end is a React single-page app (client/), the back end is a Node/Express server exposing both REST routes and a GraphQL API (server/), and it persists data in a database (server/model/database.js). Authentication is handled via Firebase, and payment via PayPal.
File structure
• Top level:
• client/ – React app, organized by feature (components/, redux/, pages/)
• server/ – Node/Express app with:
– controllers/ & routes/ (REST endpoints)
– graphql/schemas & resolvers (GraphQL)
– firebase/ (Auth config)
– paypal/ (payment integration)
– middleware/ (token verification)
– model/ (data models + DB connection)
• Bundler/config: webpack.config.js, .env files
• Deployment/build scripts in package.json
Diagramming conventions
• From Browser → REST/GraphQL endpoints (annotate “HTTP/HTTPS”)
• From API → Database (annotate “mongoose queries”)
• From Auth middleware → Firebase (annotate “verify JWT”)
• From PayPal client → PayPal API (annotate “payment request”)
• Purple clouds for external services