How uhrinandor/restaurant-orders works
Project type and purpose
• This is a full-stack “Restaurant Order” system comprising:
• An Admin web client (Next.js + Apollo + NextAuth)
• A GraphQL API (NestJS + Prisma)
• Multiple MySQL schemas (main, analytics, static)
• Redis cache
• Docker-Compose orchestration
• Purpose: let restaurant owners manage resources (tables, waiters, categories, products, orders) and view analytics.
File structure
• Top-level:
• docker-compose.yaml & init/db/init.sql → container orchestration & initial DB seed
• admin/ → Next.js Admin UI
• server/ → NestJS GraphQL API + Prisma + modules + tests
• Admin subdivides into an Apollo layer, Auth pages, Dashboard pages (resources: categories, tables, waiters), shared components.
• Server subdivides into GraphQL modules: resources (address, category, meal, order, etc.), analytics (income, product, waiter), auth, cache, filter, interceptors, Prisma clients for each DB, tests.
Extract README insights
• GraphQL API built with NestJS, documented via SpectQL
• Database is MySQL (three schemas), cache is Redis
• Fully containerized; environment variables control DB URLs, Redis URL, JWT secret, CORS domain, API port
a. Admin Client
• Next.js / React App
• Apollo Client + NextAuth → GraphQL endpoint
b. API Server
• NestJS GraphQL Gateway
• Modules / Resolvers / Services
• Guards (JWT, role), Pipes, Filters, Interceptors
c. Data Layer
• Prisma Clients → three MySQL schemas (main, analytics, static)
• Redis Cache service
d. Infrastructure
• Docker-Compose orchestrates:
– MySQL container (init via init.sql)
– Redis container
– NestJS API container
– (Optionally) Prisma migrations container
e. External / Cross-cutting
• Environment Variables (DB URLs, JWT_SECRET, ADMIN_DOMAIN)
• CORS configuration
• SpectQL docs
Relationships & interactions
• Admin UI → (HTTP + WebSocket) → GraphQL API
• GraphQL requests pass through Guards → Resolvers → Services → Prisma → MySQL
• Some queries use Redis via Cache Service / Interceptor
• Analytics module reads/writes to analytics DB; core resources use main DB; static data use static DB
• Prisma migrations use the shadow DB URLs
• Docker-Compose links DB & Redis to API container by network
Architectural patterns & principles
• Modular monolith in the API: each domain (resources, analytics, auth) is isolated in its own NestJS module
• Separation of concerns: Guards, Pipes, Interceptors handle cross-cutting concerns (auth, validation, caching)
• Repository pattern via Prisma service modules
• Frontend-backend separation: Next.js handles UI; API does business logic & data persistence