dineshkarthick21/coffee-portal-springboot

Purpose and Entry Points

JavaBite is a role-based coffee-shop management system: customers browse, order, book tables, pay, and submit feedback; staff process orders; admins manage operations. The browser app starts at frontend/src/main.jsx and routes from frontend/src/App.jsx. The Spring Boot API starts at backend/src/main/java/com/javabite/JavaBiteApplication.java.

Frontend Application Shell

React/Vite provides separate customer, admin, chef, waiter, authentication, and payment views. Shared dashboard chrome centralizes role-oriented navigation in frontend/src/layout/DashboardLayout.jsx; page areas are rooted under frontend/src/pages/Admin, frontend/src/pages/Customer, frontend/src/pages/Chef, and frontend/src/pages/Waiter. HTTP requests flow through frontend/src/api/apiClient.js to the configurable backend URL.

Authentication and Access Boundary

JWT authentication is shared across frontend and backend. Client session/token state and protected-route gating reside in frontend/src/auth/AuthContext.jsx and frontend/src/auth/PrivateRoute.jsx. Backend login, registration, password recovery, and token operations enter through backend/src/main/java/com/javabite/controller/AuthController.java, are implemented by backend/src/main/java/com/javabite/service/AuthService.java, and pass through backend/src/main/java/com/javabite/config/JwtAuthenticationFilter.java plus backend/src/main/java/com/javabite/config/SecurityConfig.java. Roles are represented by backend/src/main/java/com/javabite/entity/Role.java.

Core Operational Domains

REST controllers form the API boundary; services apply domain logic; Mongo repositories persist aggregates. The main lifecycle domains are:

• Menu and image-backed catalog: backend/src/main/java/com/javabite/controller/MenuController.java, backend/src/main/java/com/javabite/service/MenuItemService.java, backend/src/main/java/com/javabite/entity/MenuItem.java.

• Orders and kitchen/service workflow: backend/src/main/java/com/javabite/controller/OrderController.java, backend/src/main/java/com/javabite/service/OrderService.java, backend/src/main/java/com/javabite/entity/Order.java.

• Table inventory and reservations: backend/src/main/java/com/javabite/controller/BookingController.java, backend/src/main/java/com/javabite/service/BookingService.java, backend/src/main/java/com/javabite/entity/Booking.java.

• Payments: backend/src/main/java/com/javabite/controller/PaymentController.java, backend/src/main/java/com/javabite/service/PaymentService.java, backend/src/main/java/com/javabite/entity/Payment.java.

• Feedback intake and administrative status/analytics: backend/src/main/java/com/javabite/controller/FeedbackController.java, backend/src/main/java/com/javabite/service/FeedbackService.java, backend/src/main/java/com/javabite/entity/Feedback.java.

Data and Integration Flow

Requests use DTOs at the controller boundary, such as backend/src/main/java/com/javabite/dto/CreateOrderRequest.java and backend/src/main/java/com/javabite/dto/PaymentVerificationRequest.java. Services translate these to MongoDB documents and repositories, including backend/src/main/java/com/javabite/repository/OrderRepository.java, backend/src/main/java/com/javabite/repository/BookingRepository.java, and backend/src/main/java/com/javabite/repository/UserRepository.java. Payment infrastructure is configured in backend/src/main/java/com/javabite/config/RazorpayConfig.java; email, PDFs, and local file uploads are isolated in backend/src/main/java/com/javabite/service/EmailService.java, backend/src/main/java/com/javabite/service/PdfService.java, and backend/src/main/java/com/javabite/service/FileService.java.

Runtime and Deployment

Backend runtime is Java 17, Spring Boot 3.2, Maven, Spring Security, and MongoDB; configuration is under backend/src/main/resources/application.properties. The frontend is React 19 with Vite, deployed as a static/Nginx container via frontend/Dockerfile and frontend/nginx.conf. Local container orchestration provisions MongoDB and backend in docker-compose.yml; Render deployment topology is defined by render.yaml. Uploaded menu media is filesystem-backed under backend/uploads/menu, so it requires persistent volume or external object storage in production.