# fabiobatoni/daily-diet-api architecture

> Architecture diagram of the GitHub repository fabiobatoni/daily-diet-api, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-09-24). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/fabiobatoni/daily-diet-api
- Repository: https://github.com/fabiobatoni/daily-diet-api

## Overview

##### Project type and purpose
- This is a TypeScript-based Node.js REST API for managing users and their meals (a diet tracker).
- It provides endpoints to register users, authenticate requests, perform CRUD on meals, and compute user metrics.

##### File structure
- Top level: configuration files (.eslintrc.json, tsconfig.json), package.json, README.
- src/
- env/index.ts – loads environment variables (e.g. DB connection, JWT secret)
- app.ts – sets up the application: middleware, routes, error handling
- server.ts – HTTP server bootstrap (binds app to a port)
- No frontend code—pure backend.

##### README for additional insights
- Functional requirements: user signup, authentication (identify user per request), meal CRUD with timestamps, diet flag, per-user authorization, and reporting metrics (total meals, in-diet count, out-diet count, best in-diet streak).

##### Main components
a. Client (Postman or UI)
b. HTTP Server (Express or Fastify instance in server.ts)
c. Application Layer (app.ts):
- Middleware:
- Logging
- Body parser
- Authentication (JWT/session) – verifies user identity on each request
- Routes:
- /users → UserController
- /sessions → AuthController
- /meals → MealController
- /metrics → MetricsController
- Controllers → call corresponding Services
d. Services (business logic):
- UserService
- AuthService
- MealService
- MetricsService
e. Data Access Layer (Repositories/ORM):
- UserRepository
- MealRepository
f. Database (relational, e.g. PostgreSQL or SQLite)
g. Configuration (env module)
h. Optional: Error handling & logging components

##### Relationships and interactions
- Client → HTTP Server (HTTP request)
- Server loads env → initializes app
- Request → Middleware (auth check) → Route matches → Controller
- Controller → Service → Repository → Database
- Database → Repository → Service → Controller → HTTP Response → Client

##### Architectural patterns and design principles
- Layered architecture (Routing → Controller → Service → Repository → DB)
- Separation of concerns (auth in middleware, config in env module)
- Single Responsibility (each service handles one domain: users, meals, metrics)
- Dependency injection (pass repositories into services)

##### Technologies and frameworks
- Node.js + TypeScript
- Express or Fastify (inferred)
- JWT or session middleware for auth
- ORM/Query builder (e.g., Prisma, TypeORM, or Knex)
- dotenv or similar for env variables

##### Essential elements
- Entrypoint (server.ts) and app initialization (app.ts)
- Middleware chain (parsers, auth)
- Controllers for each route group
- Service layer with business logic
- Repository/ORM layer
- Environment/configuration module

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% External Actor
    Client["Client (Postman/UI)"]:::external

    %% Configuration Module
    Env["Configuration Module\n(env/index.ts)"]:::config

    %% API Layer
    subgraph "API Layer"
        direction TB
        Server["HTTP Server\n(server.ts)"]:::application
        App["Application Setup\n(app.ts)"]:::application

        subgraph "Middleware"
            direction TB
            Logging["Logging"]:::application
            BodyParser["Body Parser"]:::application
            AuthMiddleware["Authentication Middleware"]:::application
        end

        subgraph "Controllers"
            direction TB
            UserController["UserController"]:::application
            AuthController["AuthController"]:::application
            MealController["MealController"]:::application
            MetricsController["MetricsController"]:::application
        end
    end

    %% Business Logic Layer
    subgraph "Business Logic Layer"
        direction TB
        UserService["UserService"]:::application
        AuthService["AuthService"]:::application
        MealService["MealService"]:::application
        MetricsService["MetricsService"]:::application
    end

    %% Data Layer
    subgraph "Data Layer"
        direction TB
        UserRepository["UserRepository"]:::data
        MealRepository["MealRepository"]:::data
        Database["Database\n(PostgreSQL/SQLite)"]:::data
    end

    %% Data Flows
    Client -->|"HTTP Request"| Server
    Env --> Server
    Server --> App
    App --> Logging
    App --> BodyParser
    App --> AuthMiddleware
    Logging --> UserController
    BodyParser --> UserController
    AuthMiddleware --> UserController
    AuthMiddleware --> AuthController
    AuthMiddleware --> MealController
    AuthMiddleware --> MetricsController

    UserController -->|"calls"| UserService
    AuthController -->|"calls"| AuthService
    MealController -->|"calls"| MealService
    MetricsController -->|"calls"| MetricsService

    UserService -->|"uses"| UserRepository
    AuthService -->|"uses"| UserRepository
    MealService -->|"uses"| MealRepository
    MetricsService -->|"uses"| MealRepository

    UserRepository --> Database
    MealRepository --> Database

    Database --> UserRepository
    Database --> MealRepository
    UserRepository --> UserService
    MealRepository --> MealService
    UserService --> UserController
    AuthService --> AuthController
    MealService --> MealController
    MetricsService --> MetricsController
    Server -->|"HTTP Response"| Client

    %% Click Events
    click Env "https://github.com/fabiobatoni/daily-diet-api/blob/main/src/env/index.ts"
    click Server "https://github.com/fabiobatoni/daily-diet-api/blob/main/src/server.ts"
    click App "https://github.com/fabiobatoni/daily-diet-api/blob/main/src/app.ts"

    %% Styles
    classDef external fill:#87CEFA,stroke:#333,stroke-width:1px
    classDef application fill:#98FB98,stroke:#333,stroke-width:1px
    classDef data fill:#FFA500,stroke:#333,stroke-width:1px
    classDef config fill:#D3D3D3,stroke:#333,stroke-width:1px
```
