How alanvh24/raptornet_exterior_updates works
Main Components and Their Roles
• Backend – RaptorNet:
▪ Controllers (e.g., AuthController, DocenteController, DireccionAcademicaController, etc.) that accept inbound HTTP requests.
▪ DTOs and Models that represent data objects and domain entities such as “Alumno,” “Calificaciones,” “AspiranteCalificaciones,” etc.
▪ Repositories that handle data persistence (these communicate with the underlying database using JPA).
▪ Service layer components (e.g., CalificacionService, EmailService, CargaMateriasService, among others) where core business logic resides.
▪ Security components – this includes JWT utilities, filters, and Spring Security configurations (WebSecurityConfig, AuthTokenFilter, etc.) which handle authentication and authorization.
▪ Configuration files like application.properties that define runtime parameters.
• Frontend – raptornet-frontend:
– A React-based client built with modern JavaScript. It includes environment configuration (.env), entry points (like index.js, App.js), components for various roles (Admin, Docentes, serviciosEscolares, etc.), and service files that manage API calls.
• Database:
– SQL scripts are stored in the “BD” folder (with various SQL files suggesting different environments such as production, test, etc.) and the “BackupsBD” folder. These scripts indicate that an RDBMS is in use.
Relationships and Interactions
– The Frontend communicates with the Backend via RESTful HTTP calls. The API endpoints provided by the controllers support authentication, user management, academic record handling, and more.
– In the Backend, the Controllers invoke the Service layer to process business logic. These services then interact with the Repository layer which performs data operations by interfacing with the Database.
– The Security layer, including JWT utilities and filters, is integrated into the request-processing pipeline to ensure secure communication.
– The Database is central; both the backend’s Repository layer and the SQL backup/migration scripts rely on it.
Architectural Patterns & Design Principles
– The Backend follows the Model-View-Controller (MVC) pattern, where controllers (presentation layer) separate concerns from the services (business logic) and repositories (data access).
– The Security is implemented using JWT tokens and Spring Security, clearly separating concerns by intercepting and validating requests before they reach application logic.
– The Frontend is component-based, modularizing functionality by domain (e.g., Docentes, Servicios Escolares, Vinculacion) with clear separation between components, services, and utility modules.
Key Technologies/Frameworks/Libraries
– Backend: Java, Spring Boot, Maven, Spring Security, JWT, and possibly a relational database (MySQL, PostgreSQL, etc.—implied by the SQL scripts).
– Frontend: React (JavaScript), NodeJS (package.json, package-lock.json), and related libraries for routing and state management.
– Database: SQL scripts imply an RDBMS is used with potential backup and migration strategies.
Additional Details for Precision
– In the Backend, don’t simply group everything together; try detailing individual modules that stand out (such as the specialized security services and utilities in the “security” package).
– Indicate migration scripts and backups under the Database section to show schema evolution and backup strategy.
– On the Frontend side, note the existence of helper utilities (like EventBus.js, with-router.js) and service modules handling API interactions.