# adrijam18/eventease architecture

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

- Interactive diagram: https://gitdiagram.com/adrijam18/eventease
- Repository: https://github.com/adrijam18/eventease

## Overview

##### Project type and purpose
- From the file tree and README, this is the backend portion of a web-based event management system (“Event Ease”) where organizers register, log in, and create events.
- It follows a typical RESTful service pattern (Express router → controllers → models → database).

##### File structure
- Top-level “backend” directory holds all server code.
- config: database connection and Knex config
- router: Express route definitions
- controller: request handlers (business logic)
- models: data-access layer using Knex queries
- server.js: application entry point
- uploads: file storage for event assets (images, docs)
- Presence of knexfile.js indicates SQL DB (Postgres/MySQL).
- package.json lists dependencies (Express, Knex, etc.).

##### README for additional insights
- Describes the user flow: register → login → create event → add details.
- Implies authentication, session management, and CRUD operations on events.

##### Main components
a. Client (Web or Mobile UI)
- Sends HTTPS requests to the API.
b. API Layer (Express Server)
- Entry point (server.js)
- Router module (organizerRoutes.js)
c. Controller Layer
- organizerController: validates input, enforces business rules
d. Data Access Layer (Models)
- organizerModel: constructs SQL via Knex
e. Database
- Postgres/MySQL (configured in knexfile.js)
f. File Store
- Local “uploads” directory for event assets
g. (Optional) Authentication Service
- JWT or session store for organizer logins

##### Relationships and interactions
- Client → HTTP(S) → API Layer
- API Layer routes → appropriate controller method
- Controller → calls model functions → executes SQL on DB
- Controller → reads/writes files to “uploads” directory
- DB responses → controller → HTTP response back to client

##### Architectural patterns and design principles
- MVC (Router → Controller → Model)
- Layered architecture (Separation of concerns)
- Use of Knex for query building (SQL abstraction)

##### Technologies/Frameworks to highlight
- Node.js / Express for server
- Knex.js for database queries
- PostgreSQL or MySQL as RDBMS
- Local file system for uploads

##### Diagramming conventions
- Another for server layers (router, controller, model)
- Another for storage (uploads)
- From Client → Router (HTTP request)
- Router → Controller (function call)
- Controller → Model (method call)
- Model → Database (SQL over TCP)
- Controller ↔ File Store (read/write)

##### Detail
- Call out config modules (db.js, knexfile.js) as the “database connection” component
- Uploads folder as the “Asset Storage”

## Diagram (Mermaid)

```mermaid
flowchart TD
    Client["Client (Web/Mobile UI)"]:::external

    subgraph "Backend (Express Server)"
        Server["server.js (API Entry Point)"]:::server
        Router["organizerRoutes.js"]:::router
        Controller["organizerController.js"]:::controller
        Model["organizerModel.js"]:::model
        subgraph "Config"
            DBConfig["db.js (Database Connection)"]:::config
            KnexConfig["knexfile.js (DB Setup)"]:::config
        end
        FileStore["uploads (Asset Storage)"]:::storage
    end

    Database["Postgres/MySQL"]:::database

    Client -->|"JSON over HTTP(S)"| Server
    Server -->|"routes requests"| Router
    Router -->|"invokes handlers"| Controller
    Controller -->|"calls data access"| Model
    Model -->|"executes SQL over TCP"| Database
    Controller -->|"read/write files"| FileStore
    Server -->|"uses config"| DBConfig
    DBConfig -->|"reads setup"| KnexConfig
    DBConfig -->|"connects to"| Database

    click Server "https://github.com/adrijam18/eventease/blob/main/backend/server.js"
    click Router "https://github.com/adrijam18/eventease/blob/main/backend/router/organizerRoutes.js"
    click Controller "https://github.com/adrijam18/eventease/blob/main/backend/controller/organizerController.js"
    click Model "https://github.com/adrijam18/eventease/blob/main/backend/models/organizerModel.js"
    click DBConfig "https://github.com/adrijam18/eventease/blob/main/backend/config/db.js"
    click KnexConfig "https://github.com/adrijam18/eventease/blob/main/backend/config/knexfile.js"
    click FileStore "https://github.com/adrijam18/eventease/tree/main/backend/uploads"

    classDef external fill:#D0E6FF,stroke:#1E3A8A,color:#1E3A8A;
    classDef server fill:#D1FAE5,stroke:#047857,color:#065F46;
    classDef router fill:#DCFCE7,stroke:#065F46,color:#065F46;
    classDef controller fill:#FEF9C3,stroke:#713F12,color:#713F12;
    classDef model fill:#FFEDD5,stroke:#C2410C,color:#9A3412;
    classDef config fill:#FCE7F3,stroke:#831843,color:#831843;
    classDef storage fill:#E0E7FF,stroke:#4338CA,color:#4338CA;
    classDef database fill:#FEE2E2,stroke:#B91C1C,color:#7F1D1D;
```
