How rafikifred/springboot_projectassignment works
Project type and purpose
• This is a standalone backend service (a RESTful API) for an online journal (“MyDiary”).
• Purpose: expose user-management and journal-entry endpoints, persist data in MySQL, and optionally secure endpoints via JWT/OAuth.
File structure
• Top-level:
• pom.xml, Maven wrapper – standard Java/Spring Boot project
• src/main/java/com/mydiary/mydiary – application code
– controller/ (UserController.java)
– service/ (UserService.java)
– repository/ (UserRepository.java)
– model/ (User.java)
– MydiaryApplication.java (Spring Boot entry point)
• src/main/resources/application.properties – DB & JPA config
• src/test – unit/integration tests
• No “frontend” or separate microservices folders—this is a monolith with a classic layered architecture.
README for additional insights
• Exposed endpoints:
• /auth/signup, /auth/signin
• /entries CRUD
• Tech stack: Spring Boot, Spring Data JPA, MySQL, (optional) Spring Security/JWT/OAuth
• Database schema: users + journal_entries tables