How sandeepkumar-s-18/bookstore-management-system works
Project type and purpose
• This is a backend-only RESTful API for a Bookstore Management System built with Java 21 and Spring Boot.
• It exposes endpoints for book CRUD, user authentication (JWT), order processing, pagination/search, and Swagger docs.
File structure
• Top-level: pom.xml, Maven wrappers, README.
• src/main/java/com/bookstore: standard Spring Boot layout with subpackages:
• controller – REST API entry points (AuthController, BookController, OrderController)
• dto – request/response payloads
• entity – JPA entities (Book, User, Order, OrderItem)
• enumClassess – domain enums (OrderStatus, PaymentStatus, Role)
• repository – Spring Data JPA interfaces (BookRepository, UserRepository, OrderRepository)
• service & serviceImpl – business logic interfaces and implementations (AuthService, BookService, OrderService)
• security – JWT util, filter, userDetailsService, Spring Security config
• exception – global exception handler, custom ResourceNotFoundException
• src/main/resources/application.properties – DB & JWT config
• src/test – unit/integration test scaffold
Insights from the README
• Tech stack: Spring Boot, Spring Security + JWT, MySQL, JPA/Hibernate, Swagger/OpenAPI, Maven.
• Key features: role-based access (Customer/Admin), JWT auth, pagination, search, global error handling.
• Break the project into these components: Client, Security Filter, Controllers, Services, Repositories, Database, Utilities (JWT, Exception Handler, Swagger).
• Data flow (client request, token validation, service logic, DB access, response).
• Configuration (application.properties) off to the side as a note: “DB & JWT settings”.