How nicojg27/proyecto-gypsigram works
Project type and purpose
• This is a monolithic, full-stack Java web application built with Spring Boot and Maven.
• It implements an MVC pattern that manages domain entities such as Estudiante (Student), Empresa (Company), Instituto, Empleado, Certificación, Experiencia, Idioma, etc.
• Its primary purpose is to provide CRUD operations (and potentially authentication via LoginController) over those entities, serving both HTML pages and JSON endpoints.
File structure
• Top-level:
• pom.xml – Maven build file with all dependencies (Spring Boot, Spring Data JPA, Web)
• BD GypsyGram.sql – Database schema and seed scripts
• README.md – Project name
• src/main/java/com/GypsiGram/aplicacion:
• web – Controllers (REST or MVC endpoints)
• aplicacion – Service layer (business logic)
• dominio – JPA Entities and embeddable IDs
• infraestructura – Spring Data JPA Repositories
• GypsiGramApplication.java & ServletInitializer.java – Spring Boot entrypoints
• src/main/resources:
• application.properties – configuration (DB connection, ports)
• static/ – CSS, HTML, images (client-side assets)
• pages/registro*.html, vistaEmpresas.html, contactanos.html – UI templates
README
• We rely on the code layout to infer MVC layers and DB integration.
a. Main components:
1) Client (Web Browser)
2) Spring Boot Application
• Web Layer (Controllers)
• Service Layer (EmpleadoService, EstudianteService, etc.)
• Data Layer (Spring Data Repositories)
• Domain Model (JPA Entities)
3) Relational Database (MySQL/PostgreSQL/etc.)
4) Static Asset Store (served from /static folder)
5) External systems (optional—e.g., LDAP or OAuth if LoginController hooks into them)
b. Relationships and interactions:
• Browser → HTTP → Controllers → invoke Services → call Repositories → SQL → Database
• Controllers also serve static HTML/CSS/JS from the /static folder
• Entities map 1:1 to DB tables; Repositories handle CRUD via JPA
c. Architectural patterns/design principles:
• Layered MVC (Separation of concerns: Web / Business / Data)
• Dependency Injection (Spring Beans wired via @Service, @Repository, @Controller)
• Domain-Driven Design hints (rich domain model under dominio package)
• Convention over configuration (Spring Boot auto-configuration)
d. Key technologies and frameworks:
• Spring Boot (embedded Tomcat, auto-configuration)
• Spring MVC (Controllers, request mappings, view resolvers)
• Spring Data JPA (Repository interfaces, Entity classes)
• Maven (build lifecycle, dependency management)
• Thymeleaf or static templates (though static folder suggests plain HTML)
• Relational DB (SQL schema in BD GypsyGram.sql)