How buiduynguyenn/pet_care_management works
Project type and purpose
• This is a standalone Spring Boot backend for a Pet Care Management system.
• It exposes REST endpoints (Appointment, Blog, Cart, Order, Pet, Product, Service, ServiceReview, User, Contact, Chat) and a WebSocket endpoint for real-time chat.
• It handles authentication/authorization via JWT, file uploads (albums, pet images, product images), and data persistence via Spring Data JPA.
File structure
• Top-level files: pom.xml (Maven build), application.properties (configuration), uploads/ (local file storage).
• src/main/java/com/pet_care_management/pet:
• config: SecurityConfig (JWT filter), WebSocketConfig
• controller: HTTP controllers for each domain
• dto: request/response objects for API layer
• entity: JPA entities representing tables
• repository: Spring Data JPA interfaces
• service + service.impl: business logic layer
• security: JwtUtil, JwtAuthenticationFilter
• PetApplication.java: main Spring Boot entry point
• resources/static/chat-test.html: simple WebSocket client
• src/test: unit tests for the application
Key insights from README
• Minimal README, but project name (“Pet Care Management Backend”) confirms backend role
Detail
• Domain controller and its corresponding service/repository if space allows
• Call out configuration classes (SecurityConfig, WebSocketConfig) as part of the control plane
• JWTUtil and JwtAuthenticationFilter as part of the security flow
• Uploads/ directory as an external resource the backend writes to and reads from