How idiotman-2212/busticketbooking-fullstack works
Main system components
• Backend API Server (BusTicketBooking-Backend): This module is built using Spring Boot and organized with a clear layered structure (controllers, services, repositories, models, DTOs, and configurations). It handles authentication, booking, notifications, reports, payment history, and more.
• Notification Scheduler Service: A dedicated Spring Boot application tasked with managing scheduled tasks for notification (and potentially email messaging) related to bookings.
• Frontend – Admin Application: A ReactJS application that provides an admin dashboard covering management of buses, drivers, tickets, users, reports, etc.
• Frontend – Customer Application: A ReactJS application dedicated to the customer experience (booking tickets, managing profiles, viewing notifications, etc.).
• Database: A MySQL backend to persist data (with provided SQL scripts for schema creation).
• External Services: (Implicitly) any external email or SMS services might be used by Notification Scheduler, or other third-party services integrated within the application.
Relationships and interactions between components
• Backend API Server communicating with the MySQL Database. This encompasses CRUD operations (using Spring Data repositories) and interactions defined in the service layer.
• Swagger/OpenAPI documentation as a component within the backend (accessible at http://localhost:8080/swagger-ui/index.html#) to indicate API documentation.
Architectural patterns and design principles
• Separation of Concerns – Clearly delineate between the Admin and Customer frontends as separate apps, each with its own folder and routing structure.
• Microservices / Decoupled Services – Represent the Notification Scheduler Service as an independent module with a well-defined role, highlighting its scheduling and messaging responsibilities.
• Configured external integrations – Although not detailed to the lowest level, represent where external services (email/SMS) might interface with your Notification service.
Relevant technologies and frameworks
• Spring Boot, Maven, Java – For backend API and Notification service.
• ReactJS – For both the Admin and Customer interfaces.
• MySQL – As the database.
• Maven for build and dependency management.
• Swagger/OpenAPI – For API documentation.
• Additional utilities and configuration classes (like WebSocket configuration, JWT for authentication, asynchronous processing, etc.) can be noted within the backend module.