How arishem51/rm-app works
1. A backend built with Spring Boot (Java and Maven based) – which serves as a RESTful API server with controllers, services, data transfer objects (DTOs), entities, repositories, and configuration for security, JWT handling, exception management, and more.
2. A frontend built with Next.js (React framework) – featuring a full-fledged web application that includes various pages (authentication, dashboard, profiles, and detailed modules for categories, orders, shops, warehouses, etc.), components, hooks, and service utilities to call backend endpoints.
Main components
a. Frontend:
• Next.js application that runs on port 3000.
• Pages for authentication (sign-up, sign-in, forgot/reset password), the dashboard, and differentiated modules (categories, orders, products, etc.).
b. Backend:
• This is the Spring Boot application running on port 8080.
• The backend is organized into packages such as config, controllers, services, repositories, DTOs, entities, and security.
• Components for authentication, business logic for orders, inventory, categories, partners, and more.
c. Database:
• Although not directly visible as a folder, the README indicates migrations and database seeds (using Flyway). This suggests a relational database (SQL Server, based on the migration configuration).
• That the backend interacts with the database for persistence and retrieval.
d. Migration & Configuration:
• That database migrations (Flyway) are part of the system, triggered by Maven commands.
• Configuration files (application.properties, .env.example) that manage environment settings.
Relationships and interactions
• Optionally, delineate the migration tool (Flyway) as part of the backend component that ensures the database schema is up-to-date.
Design principles and patterns
• The backend adheres to a layered architecture (Controller → Service → Repository) and utilizes standard Spring Boot practices such as dependency injection and security configurations.
• The frontend is built with a modular, component-based pattern, leveraging Next.js’s file structure for routing and React’s component system.
• The separation of concerns is clear, with the monorepo structure keeping both projects in sync but structurally independent.
Technologies and frameworks
• Backend: Spring Boot, Maven, Flyway for migrations, JWT for authentication, and typical Java libraries for validation and exception handling.
• Frontend: Next.js, React, Tailwind CSS, and testing tools like Jest and Cypress.
• Other: A SQL Server database is used as per the migration command details.