How akshat-kumawat20/student-management-system works
This is a monolithic, server-rendered full-stack web application:
• Backend: Spring Boot 3.x (Java 17), Spring MVC, Spring Data JPA, Spring Security
• Frontend: Thymeleaf templates rendered on the server + static CSS
• Database: MySQL
• Domain: Student Management (CRUD + search + pagination + CSV export + image upload + auth)
• Request flow: Browser → Spring MVC controllers → service/data access → MySQL
• Security boundaries: unauthenticated vs authenticated endpoints
• Server-side rendering: controllers returning Thymeleaf views
• Supporting features: file/image upload handling, CSV export response
File structure analysis (map folders/files to architectural blocks)
From the tree, the system decomposes into these concrete components:
Entry point / Application bootstrap
• MyprojectApplication.java
Spring Boot main application: component scanning + auto-configuration.
Web layer (MVC controllers)
• HelloController.java (likely a simple route)
• controller/StudentController.java
Owns HTTP endpoints for students (list/search/pagination, add/edit/delete, upload photo, CSV download).
Configuration layer
• config/SecurityConfig.java
Spring Security filter chain, login/logout, protected routes.
• config/WebConfig.java
MVC config (view resolvers, resource handlers, maybe upload path mappings).
Persistence layer (JPA)
• entity/Student.java
JPA entity mapping of student table/columns (and likely photo path/filename fields).
• repository/StudentRepository.java
Spring Data repository (CRUD + query methods for search/pagination).
Views & static assets (server-rendered UI)
• resources/templates/*.html
Thymeleaf views: students.html, add-student.html, edit-student.html, login.html.
• resources/static/css/style.css
Static styling served directly.
Runtime configuration
• resources/application.properties
DB URL/user/pass, JPA settings, multipart upload limits, etc.
Build/test tooling
• pom.xml + Maven wrapper
• MyprojectApplicationTests.java
• README mentions JaCoCo coverage (even if config isn’t visible in tree).
Important architectural note: There is no explicit service package in the tree. That strongly suggests the controller may call the repository directly (simple layered architecture: Controller → Repository), unless services are defined elsewhere not shown.
Spring Boot Web App (Monolith)
• Sub-labels: Spring MVC, Thymeleaf, Spring Security, Spring Data JPA
File Storage for uploaded photos
5. (Optional) CSV Export (not a separate system, but show as an output path: controller returns text/csv / attachment)
• Browser → Spring Boot: HTTP(S)
• Spring Boot → MySQL: JDBC / JPA
• Spring Boot → File storage: read/write uploaded images
• Spring Boot → Browser: HTML (Thymeleaf) + CSS/static resources + CSV download responses
Web/MVC
• StudentController
• HelloController
Security
• SecurityConfig (and conceptually: Security Filter Chain, Authentication Provider)
• Login page: login.html
View layer
• Thymeleaf templates: students.html, add-student.html, edit-student.html, login.html
• Static assets: style.css
Persistence
• StudentRepository (Spring Data JPA)
• Student entity
Configuration
• WebConfig
• application.properties (externalized config feeding DB + upload settings)
• Controllers → Thymeleaf templates (return view names + model)
• Controllers → Repository (CRUD/search/page)
• Repository → MySQL (via JPA/Hibernate)
• Controllers → File Storage (upload photo / resolve photo URL)
• Security Filter Chain intercepts Browser → Controllers (show as a gate in front of controller routes)
Architectural patterns / principles to call out
• Monolith with layered MVC: Controller (web) + Repository (data access) + Entity (domain/persistence model) + Views (Thymeleaf).
• Server-side rendering: Thymeleaf templates are first-class UI components, not a SPA.
• Security as a cross-cutting concern: Spring Security filter chain in front of endpoints.
• Convention-over-configuration: Spring Boot auto-config (DB, MVC, Security).