How suyog-ghadage/insuranceproject works
Project type and purpose
• This is a monolithic Spring Boot backend service (“HealthInsurance”) implementing a RESTful API for managing health‐insurance domain objects (users, policies, claims, appointments, documents, FAQs, hospitals, doctors, etc.).
• It performs CRUD operations, user authentication/authorization (with JWT), email notifications, and “super-admin” alerts.
File structure
• Top level:
• pom.xml, mvnw scripts, application properties
• src/main/java/com/crud:
– confg: security (SecurityConfig, JwtAuthFilter, JwtUtil, entry points, CustomUserDetailsService)
– controller: one REST controller per domain concept (UserController, ClaimController, AppointmentController, AdminController, etc.)
– dto: input/output data transfer objects
– entity: JPA entities mapping to database tables
– enums: domain enumerations (Role, PolicyStatus, etc.)
– repository: Spring Data JPA repositories
– service: service interfaces
– serviceimpl: service implementations
– util: supporting utilities (SuperAdminNotifier, EmailServiceImpl)
• src/main/resources/application.properties for DB and mail configuration
• src/test: basic Spring Boot integration test
• BUILD: packaged as an executable JAR
Key architectural observations
• Layered architecture (Controller → Service → Repository → Database)
• Spring Security + JWT filter chain for authN/authZ
• Domain-driven modules organized by package
• External SMTP/email service integration
• No separate frontend—this is purely a backend microservice