How leocamachocr/spring-boot-base-app works
Project Type and Purpose
• Monolithic, server-side Spring Boot application
• Exposes REST API endpoints
• Stores data in an in-memory H2 database (managed via Liquibase changelogs)
• Applies CQRS: separate write (commands) and read (queries) flows
• Implements JWT-based security and CORS configuration
Main Architectural Layers and Components
A. External Clients
– REST clients (e.g., Postman, Swagger UI or any frontend)
B. Web/API Layer
– Spring MVC REST Controllers
• LoginUserController
• RegisterUserController
• UserQueriesController
– Exception Handling
• ExceptionManagerController
C. Security Layer
– CorsConfig (CORS rules)
– WebSecurityConfig (HTTP security rules)
– JwtRequestFilter (extracts & validates JWT)
– AuthenticationErrorHandlingEntryPoint
– JwtProvider (token creation & validation)
– UserAuthenticationQuery (loads user for auth context)
– Session & SessionContextHolder (stores auth info in thread context)
D. Application (Business) Layer – CQRS Handlers
– Command Handlers
• RegisterUserHandler → EncodePasswordHandler → UserRepository.save
• LoginUserHandler → JwtProvider → generate token
– Query Handlers
• GetCurrentUserQuery → UserRepository.findById → map to UserResponse
E. Persistence Layer
– JPA Entities & Repositories
• UserEntity
• UserRepository (Spring Data JPA)
– Liquibase changelogs (DB migrations)
– H2 in-memory database
F. Shared/API Types
– Request/Response DTOs (LoginUserRequest, RegisterUserRequest, LoginResponse, UserResponse, ErrorResponse)
G. Test Suite
– Cucumber API tests (features, steps, runners)
– Unit tests for handlers, validators, structure (ArchUnit)
Relationships & Data Flows
1. Client → REST Controller
2. Controller → Security Filter Chain (JwtRequestFilter + WebSecurityConfig)
3. Controller → (via dependency injection) → appropriate Command or Query Handler
4a. Command Handler → EncodePasswordHandler (if required) → UserRepository → H2 DB
4b. Query Handler → UserRepository → H2 DB
5. Repository responses → Handler → Controller → HTTP Response
6. Liquibase applies on startup: XML changelog → H2 schema/data
Architectural Patterns
• Layered architecture (API, Security, Application, Persistence)
• CQRS: separate command vs query handlers
• Single Responsibility Principle: one handler per use case; one controller per resource
• Dependency Injection via Spring Boot
• Security filter chain for JWT auth
Elements
• Clear labels (component names + package paths if needed)