How puncho-dev/ahp_ludoteca works
Project Type and Purpose
• This is a full-stack web application (“Proyecto-Tutorial de Ludoteca”) for managing video-game lending: clients, authors, games, and loans.
• The frontend is an Angular 17+ SPA (TypeScript, Angular Material, Bootstrap, RxJS). The backend is a Spring Boot monolith (Java 21, Spring Web, Spring Data JPA, H2 DB, Maven).
File Structure Highlights
• Top-level directories:
• cliente/ludoteca-test → Angular client
• servidor/tutorial → Spring Boot server
• Frontend: organized by feature modules (author, category, client, game, loan) under src/app.
• Backend: organized by package per feature (author, category, client, game, loan) plus common (pagination, search criteria), config, and resources.
Key Architecture Components
a. Frontend SPA
• Components (author-list, author-edit, client-list, loan-list, etc.)
• Services using HttpClient → REST API calls
• Angular router for navigation
b. REST API Layer (Spring Controllers)
• AuthorController, ClientController, GameController, LoanController, CategoryController
c. Business Logic (Spring Services)
• Service interfaces + implementations (AuthorServiceImpl, etc.)
• Validation annotations (Spring Validation)
d. Data Access (Spring Data JPA Repositories)
• AuthorRepository, ClientRepository, etc.
e. Persistence
• H2 in-memory DB for dev/tests
• Entities, DTOs, search/pagination criteria
f. Build & Dev Tools
• Frontend: Vite dev server, Angular CLI
• Backend: Maven, JUnit 5 tests
Relationships & Data Flows
• Browser → (1) Angular Router/Components → (2) HttpClient GET/POST/PUT/DELETE → (3) Spring Controllers → (4) Service Layer → (5) Repository → (6) H2 DB
• The server returns DTOs back up the chain, HttpClient Observables feed Component views.
Architectural Patterns & Principles
• Layered architecture (Presentation → API → Service → Repository → Data)
• Feature-based modularization in frontend
• DTO pattern + ModelMapper (ModelMapperConfig)
• Pagination & filtering via common SearchCriteria and PageableRequest