How belhajmokhlis/intrabank works
Project type and purpose
• This is a full-stack web application called “Intrabank.”
• Backend: Java Spring Boot monolith implementing REST endpoints for authentication (JWT), user/admin management, document/category/version management, file upload, and profile.
• Frontend: Angular SPA using NgRx for state management, with routes & guards for auth, admin, documents, workflows, profile, and shared UI components.
File structure
• Top level splits into two roots: intrabank-backend/ and intrabank-frontend/.
• Backend layers follow MVC + service + repository + security + config + mapper + dto patterns.
• Frontend features a core folder (guards, interceptors, generic services), a features folder (UI components per domain), shared folder, and a store folder (actions/effects/reducers/selectors/state).
• Presence of application-*.properties, Maven wrapper, Spring Security config, JWT filter, CORS config.
• Angular side includes environment configs, tailwind, proxy script, route definitions, and NgRx setup.
Detail but keep clarity
• Layers (UI, state management, HTTP pipeline, security, controllers, services, repositories).
• Data flow for a key use case (e.g. “Upload new document”: UI → DocumentUploadComponent → DocumentService → HTTP Interceptor → DocumentController → DocumentServiceImpl → FichierDocumentRepository + save file → response → update NgRx store).
• Avoid over-clustering: group related controllers/services but show each layer’s boundary.