# rvkisme/quickmeet architecture

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

- Interactive diagram: https://gitdiagram.com/rvkisme/quickmeet
- Repository: https://github.com/rvkisme/quickmeet

## Overview

##### What this project is (type + purpose)
**QuickMeet** is a **minimal real-time “room” meeting app** with **no login and no data persistence** (“meet your friends in a room without any data saving or login”).

From the tree, it’s a **small client–server web application**:
- **Client**: static frontend (`client/index.html`, `client/style.css`, `client/client.js`)
- **Server**: Node.js backend (`server/server.js` + `server/package.json`), likely serving the client and handling “room” coordination (commonly via HTTP + WebSocket).
- **No database**: there’s no `db/`, migrations, ORM config, or persistence layer.

- what `server/server.js` actually does (HTTP only vs WebSocket vs WebRTC signaling),
- what `client/client.js` actually does (polling vs WebSocket vs WebRTC peer connections).

##### Top-level
- `client/` → purely frontend assets. This suggests a single-page-ish flow (even if not a SPA framework).
- `server/` → self-contained Node service with NPM dependencies (`package.json`, `node_modules/`).

##### Important implications
- **Monolith, not microservices**: only one backend service exists.
- **Likely ephemeral state**: rooms probably exist in server memory; “no data saving” implies no durable storage.
- **Network boundary**: browser ↔ node server is the primary boundary; if meetings are truly peer-to-peer, there may be browser ↔ browser media paths.

##### What to extract from README (and what’s missing)
README only states product intent:
- “room” concept (implies room IDs, join/leave, member list)
- “no data saving or login” (implies no auth provider, no DB)

- **No persistent storage**
- **No authentication / identity provider**
- **Room state is transient** (most likely in-memory)

##### Browser Client
- `index.html` (UI shell)
- `style.css` (presentation)
- `client.js` (room join logic, event handling, real-time messaging/media setup)
##### Node.js Server
- `server.js` (HTTP routing + real-time room coordination)
- NPM dependencies (from `package.json`) — label major frameworks once confirmed (e.g., Express, ws, Socket.IO)
##### In-memory Room State (within server process)
- rooms map, participants list, ephemeral session/connection tracking
##### (Conditional) Peer-to-peer Media/Data Plane
- If `client.js` uses WebRTC: add **Browser ↔ Browser** media streams (audio/video/data channels)
- Server then becomes **signaling/coordination** only (SDP/ICE exchange), not media relay.

##### Static asset delivery
- Browser → Node Server: `HTTP GET /` (serves `index.html`)
- Browser → Node Server: `HTTP GET /client.js`, `HTTP GET /style.css` (static assets)

##### Room join + real-time coordination
One of these will be true—confirm by inspecting `server.js`/`client.js`:
- Browser ↔ Node Server: **WebSocket** (or Socket.IO) for:
- create/join room
- broadcast presence (join/leave)
- exchange meeting metadata

##### (If WebRTC) Signaling vs media
- Browser A ↔ Node Server ↔ Browser B: signaling messages (offer/answer/ICE)
- Browser A ↔ Browser B: media streams (SRTP)
- **Control plane** (via server)
- **Media plane** (P2P between browsers)

##### Architectural patterns/design principles used
- **Stateless persistence**: “No DB; rooms are ephemeral”
- **Single backend process**: Node server handles all coordination
- **Client-heavy behavior**: core UX and meeting logic lives in `client.js`
- **Real-time communication**: WebSocket/Socket.IO (if present) and/or WebRTC (if present)

##### Relevant technologies/frameworks/libraries
- If `express` is used: label backend as “Node.js + Express”
- If `socket.io` is used: label realtime as “Socket.IO”
- If `ws` is used: label realtime as “WebSocket (ws)”
- If WebRTC APIs appear in `client.js`: label “WebRTC (RTCPeerConnection)”

##### Practical advice: “separate into as many components as possible” (without overthinking)
- Client UI shell vs client logic (`index.html` vs `client.js`)
- Server HTTP/static hosting vs realtime room coordinator
- In-memory state as an explicit subcomponent
- Control plane vs media plane (if WebRTC)

Use this as your initial structure, then refine after checking `server.js`/`client.js`:

- **[Browser Client]**
- UI (index.html/css)
- Room/RTC logic (client.js)
- ↔ **(WebSocket/Socket.IO)** ↔ **[Node Server]**
- **[Node Server]**
- Static file serving (client/)
- Room coordinator (join/leave/broadcast)
- In-memory room registry (no persistence)
- **(Optional if WebRTC)**:
- Browser A ⇄ Browser B (P2P media/data)
- Node server only for signaling messages

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% =======================
    %% Actors / Environment
    %% =======================
    U["User"]:::actor

    subgraph "Client Device (Trust Boundary)"
        B["Browser Client"]:::client

        subgraph "client/ (Static Frontend)"
            UI["UI Shell (HTML)"]:::clientFile
            CSS["Styling (CSS)"]:::clientFile
            CJ["Room Join + Real-time Logic (JS)"]:::clientFile
        end
    end

    NET["Public Network (Internet/LAN)"]:::network

    subgraph "Server Host (Trust Boundary)"
        S["Node.js Server"]:::server

        subgraph "server/ (Backend)"
            HTTP["HTTP Static File Serving"]:::serverComp
            RTC["Real-time Room Coordinator"]:::serverComp
            MEM["In-memory Room State (Ephemeral)"]:::memory
            PKG["Dependencies Config (NPM)"]:::serverFile
            LOCK["Dependency Lockfile"]:::serverFile
            MODS["Installed Runtime Dependencies"]:::serverDir
        end

        NOTE1["No Authentication Provider\n(No login / no identities)"]:::note
        NOTE2["No Persistent Storage\n(No DB; rooms exist only in memory)"]:::note
    end

    %% =======================
    %% High-level relationships
    %% =======================
    U -->|"uses"| B
    B -->|"renders"| UI
    B -->|"applies"| CSS
    B -->|"executes"| CJ

    %% Network boundary
    B --> NET --> S

    %% Static asset delivery
    CJ -->|"GET / (HTTP)"| HTTP
    UI -->|"GET index.html (HTTP)"| HTTP
    CSS -->|"GET style.css (HTTP)"| HTTP
    CJ -->|"GET client.js (HTTP)"| HTTP

    %% Real-time coordination (protocol unknown -> generic)
    CJ <-->|"real-time_events (WebSocket/Socket.IO?)"| RTC

    %% Ephemeral room lifecycle
    RTC <-->|"create/join/leave/broadcast"| MEM

    %% Dependencies (build/runtime)
    S -->|"loads_config"| PKG
    PKG -->|"pins_versions"| LOCK
    S -->|"requires_modules"| MODS

    %% Explicit non-components
    MEM -.->|"no_write_to"| NOTE2
    RTC -.->|"no_auth_calls"| NOTE1

    %% =======================
    %% Optional WebRTC plane (conditional)
    %% =======================
    subgraph "Optional: Peer-to-Peer Media/Data Plane (If WebRTC is used)"
        direction TB
        A["Browser A (Peer)"]:::client
        B2["Browser B (Peer)"]:::client
        A <-->|"audio/video/data (P2P SRTP/DataChannel)"| B2
    end

    CJ -.->|"signaling (offer/answer/ICE?)"| RTC
    RTC -.->|"relays_signaling"| A
    RTC -.->|"relays_signaling"| B2

    %% =======================
    %% Click events (component_mapping)
    %% =======================
    click UI "https://github.com/rvkisme/quickmeet/blob/main/client/index.html"
    click CSS "https://github.com/rvkisme/quickmeet/blob/main/client/style.css"
    click CJ "https://github.com/rvkisme/quickmeet/blob/main/client/client.js"
    click S "https://github.com/rvkisme/quickmeet/blob/main/server/server.js"
    click PKG "https://github.com/rvkisme/quickmeet/blob/main/server/package.json"
    click LOCK "https://github.com/rvkisme/quickmeet/blob/main/server/package-lock.json"
    click MODS "https://github.com/rvkisme/quickmeet/tree/main/server/node_modules/"

    %% =======================
    %% Styles
    %% =======================
    classDef actor fill:#FFF4CC,stroke:#C9A800,stroke-width:1.5px,color:#1F1F1F
    classDef client fill:#D6ECFF,stroke:#1D70B8,stroke-width:1.5px,color:#0B1B2B
    classDef clientFile fill:#EAF5FF,stroke:#1D70B8,stroke-width:1.2px,color:#0B1B2B
    classDef network fill:#EFEFEF,stroke:#666,stroke-width:1.2px,color:#222
    classDef server fill:#DFF7E6,stroke:#0B7A3B,stroke-width:1.5px,color:#0B1B2B
    classDef serverComp fill:#EDFBF1,stroke:#0B7A3B,stroke-width:1.2px,color:#0B1B2B
    classDef memory fill:#FFF0F0,stroke:#B3261E,stroke-width:1.5px,color:#2B0B0B,stroke-dasharray: 5 5
    classDef serverFile fill:#F2FFF6,stroke:#0B7A3B,stroke-width:1.2px,color:#0B1B2B
    classDef serverDir fill:#F2FFF6,stroke:#0B7A3B,stroke-width:1.2px,color:#0B1B2B
    classDef note fill:#FFF7E6,stroke:#B86B00,stroke-width:1.2px,color:#2B1B0B,stroke-dasharray: 4 4
```
