How facuvillalba44/backenditsu works
Main Components
a. Client/Consumer Layer (External HTTP Clients): Represent external clients (web portals, mobile apps, etc.) sending HTTP requests to the service.
c. Service Layer (Business Logic): The “servicio” package contains interfaces (e.g., ICarreraServicio) and their concrete implementations (e.g., CarreraServicio). Represent this as a separate layer where business rules and domain logic are implemented.
d. Data Access Layer (Repository/DAO): The “repositorio” package includes repositories (e.g., CarreraRepositorio, UsuarioRepositorio) that manage persistence. This layer will abstract away the database operations.
e. Domain Model: The “modelo” package contains domain entities (e.g., Carrera, Materias, Notas, Usuario). Represent these as data models that migrate through layers.
g. Database: External to the application, a MySQL database is envisioned (given SQL scripts “datos_iniciales.sql” and “estructura.sql”) which acts as the persistent storage.
Relationships and Interactions
• Incoming requests from clients first hit the Controllers, which then delegate to the corresponding Service classes.
• The Service classes coordinate business logic and delegate data persistence operations to the Repository layer.
• The Repository layer communicates with the underlying MySQL database.
• The configuration components (e.g., SecurityConfig and JwtAuthenticationFilter) mediate authentication and environment setup across the API.
Architectural Patterns and Design Principles
• The project follows a layered (n-tier) architecture: separation between presentation (controllers), business logic (services), and data access (repositories).
• It also uses dependency injection and the repository pattern (as seen with Spring Boot’s typical development pattern).
• For security, JWT authentication is integrated to secure endpoints via Spring Security.
Relevant Technologies and Frameworks
• Java and Maven (pom.xml is used) as the project’s backbone.
• Spring Boot as the foundation of the API, with Spring Security for authentication.
• JWT for token-based security.
• SQL/MySQL as the database backend.
• DotenvConfig indicates environment variable management.