How briansittmann/caloria-backend works
Project type and purpose
• This is a monolithic Java backend service (Spring Boot) that exposes RESTful APIs for a nutritional coaching application (“CalorIA Backend”).
• It handles user registration/authentication, user profile goals, daily food logging, recipe catalog, and macro-nutrient calculations. It persists data in MongoDB and will call an external AI service (OpenAI) for food analysis.
File structure
• Top-level: pom.xml, mvnw, README.md, token.txt
• src/main/java/com/caloria:
• config: Spring configuration classes (Jackson, Security, Swagger, OkHttpClient, JWT filter)
• controller: REST controllers (AuthController, ComidaController, DiaController, PerfilController, RecetaController)
• dto: Data Transfer Objects for requests/responses
• model: Domain entities (Usuario, Receta, Alimento, Dia, etc.)
• repository: Spring Data MongoDB repositories
• service: Business logic (AuthService, UsuarioService, DiaService, Catalogo services, CaloriasCalculator, JwtService, IAService)
• utils: supporting utilities (RoundingUtils)
• src/main/resources/application.properties: app configuration
• Testing under src/test/java
README for additional insights
• Tech stack: Java 11+, Spring Boot, MongoDB, Lombok, Maven, upcoming OpenAI integration
• No frontend—focus entirely on backend API
a. Components
1. API Layer – Spring MVC Controllers
2. Security Layer – SecurityConfig + JwtAuthenticationFilter
3. Service Layer – business services (AuthService, UsuarioService, DiaService, IAService, etc.)
4. Data Access Layer – Spring Data Repositories
5. Database – MongoDB instance/cluster
6. External Service – OpenAI API (via OkHttpClient)
7. Configuration Modules – JacksonConfig, SwaggerConfig
b. Relationships & Data Flow
• Incoming HTTP request → SecurityFilter → Controller → Service → Repository → MongoDB
• Service IAService → OkHttpClient → OpenAI API → DTO response → Controller → Client
• Controllers return JSON; JacksonConfig handles serialization
• SwaggerConfig exposes /swagger-ui for API docs
c. Architectural patterns/design principles
• Layered architecture (Controller → Service → Repository)
• Separation of concerns: DTO vs. domain model
• JWT-based stateless authentication
• External API integration via client config
d. Key technologies/frameworks
• Spring Boot (web, security, data-mongodb)
• Spring Security + JWT
• Spring Data MongoDB
• Swagger (Springfox)
• OkHttp client
• Lombok (code generation)
Essential architectural elements to capture
• The security filter chain (JwtAuthenticationFilter) sitting before controllers
• The separation of DTOs vs. domain models
• The CaloriasCalculator and IAService under “Business Logic”
• The fact that all data persistence uses MongoDB
• The Swagger UI endpoint as part of the API module