How brayancortes22/sprintboot_carlos_julio works
Main Components
a. Front-end Client:
• Located under the "front-end/gestion" directory.
• Built with React (hinted by files like App.jsx, main.jsx) and styled using TailwindCSS.
• Likely communicates with the REST API hosted on the back-end.
b. Back-end API (Spring Boot Application):
• Located in "back-end/sprint-boot".
• Contains distinct packages:
• Controllers (handling incoming HTTP requests and routing them to the correct service).
• Models (representing the entities such as Aprendiz, Certificados, Cursos, Lecciones).
• Repositories (interfaces for data access using Spring Data JPA).
• Services (business logic and interaction between controllers and repositories).
• DTOs (data transfer objects for API communication).
• Includes a well-defined structure that maps closely to REST endpoints as documented in the README.
c. Database:
• A MariaDB/MySQL database with configuration details provided in application.properties.
• The "base_de datos" directory includes an SQL script (Sena.sql) to establish the database structure and initial data.
Relationships and Interactions
• The Front-end client makes HTTP requests (GET, POST, PUT, DELETE) to the Back-end API endpoints.
• The back-end REST controllers receive the requests, forward them to the corresponding service classes.
• Service classes encapsulate business logic, call repository methods to perform CRUD operations on the database.
• The Data Transfer Objects (DTOs) are used to pass structured data between the client and the server.
• The database stores the persistent state for the application (Aprendices, Cursos, etc.), with ORM mapping configured via Spring Data JPA.
• Optional: Include representation of tests and configuration files that support these operations (like application.properties and Maven build files).
Architectural Patterns and Design Principles
• Layered Architecture:
• Presentation Layer (Controllers) handles the incoming requests.
• Business Logic (Services) contains application logic.
• Data Access Layer (Repositories) interacts with the MySQL/MariaDB database.
• Use of DTOs for decoupling the internal model from external data representation.
• RESTful API design:
• Clear endpoint definitions for each entity (Aprendiz, Cursos, Lecciones, Certificados).
• CRUD operations with standardized response and error codes.
• Separation of Concerns: The project clearly separates the front-end and back-end responsibilities, enabling independent development and scalability.