# cleverprogrammers/nodejs-zoom-clone architecture

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

- Interactive diagram: https://gitdiagram.com/cleverprogrammers/nodejs-zoom-clone
- Repository: https://github.com/cleverprogrammers/nodejs-zoom-clone

## Overview

##### Project Type and Purpose
- This is a real-time, full-stack Zoom-style video conferencing clone built with Node.js.
- It uses Express.js to serve pages and static assets, EJS templates for HTML rendering, Socket.io for real-time signaling, and PeerJS (WebRTC) for peer-to-peer media streaming.

##### File Structure Analysis
- server.js: the single Node.js entry point. Sets up HTTP server, Express routes, Socket.io and PeerJS servers.
- public/: static assets (client-side JavaScript and CSS).
- views/: EJS templates (room.ejs) to render the video conferencing page.
- package.json, package-lock.json: Node.js dependencies (express, socket.io, peer, etc.).

##### Key README Insights
- Confirms Node.js, JavaScript, and MongoDB (though no DB code present).
- Focus is on building the UI, real-time signaling, and P2P media.

##### Main Components
a. Client (Browser)
- Loads HTML (EJS) + CSS + script.js from the server.
- Connects to:
- Socket.io server (for join/leave and user-connect/disconnect events).
- PeerJS server (WebRTC signaling → establishes P2P media connections).
b. Express Server (server.js)
- Serves static assets (public/) and renders views (views/room.ejs).
- Hosts:
- HTTP endpoint for “/:room” and “/” routes.
- Socket.io namespace for signaling.
c. (Optional) Database
d. External Services
- WebRTC NAT traversal (STUN/TURN servers) if configured.
- CDN for static assets (optional).

##### Component Relationships and Data Flows
- User navigates to “/roomID” → Express renders room.ejs → client JavaScript boots.
- Client opens Socket.io connection → “join-room” event → server tells existing clients to “user-connected”.
- Each client calls PeerJS.connect() → obtains peer ID → server broadcasts peer ID to room.
- Clients exchange WebRTC offer/answer via PeerJS server → establish direct P2P audio/video streams.
- Socket.io handles text chat or signaling fallbacks; PeerJS handles media channels.

##### Architectural Patterns and Principles
- Monolithic Node.js backend combining HTTP and real-time APIs.
- Separation of concerns:
- Presentation: EJS views + static assets.
- Signaling: Socket.io events.
- Media relay: PeerJS (WebRTC).
- Client-driven P2P mesh topology: each client links to every other client in a room.

##### Final Checklist
- Components clearly boxed and labeled.
- Callouts for key events or data formats (JSON, SDP).
- P2P mesh with multiple client instances and direct connections.

## Diagram (Mermaid)

```mermaid
graph TB

  subgraph "Client (Browser)" 
    direction TB
    Browser1["Browser Instance 1"]:::client
    Browser2["Browser Instance 2"]:::client
    roomEJS["room.ejs"]:::client
    scriptJS["script.js"]:::client
    styleCSS["style.css"]:::client
  end

  subgraph "Node.js Server" 
    direction TB
    Express["Express.js\n(HTTP Server)"]:::server
    SocketIO["Socket.io\n(Signaling)"]:::server
    PeerJS["PeerJS Server\n(WebRTC Signaling)"]:::server
    packageJSON["package.json"]:::server
    packageLock["package-lock.json"]:::server
  end

  subgraph "External Services" 
    direction TB
    MongoDB["MongoDB\n(Optional)"]:::external
    STUNTURN["STUN/TURN\n(NAT Traversal)"]:::external
    CDN["CDN\n(Optional Static)"]:::external
  end

  %% Connections: HTTP Layer
  Browser1 -->|"HTTP GET"| Express
  Browser2 -->|"HTTP GET"| Express
  Express -->|"serves HTML/CSS/JS"| roomEJS
  Express -->|"serves HTML/CSS/JS"| scriptJS
  Express -->|"serves HTML/CSS/JS"| styleCSS

  %% Connections: Socket.io Signaling
  Browser1 -->|"WS: join-room"| SocketIO
  Browser2 -->|"WS: join-room"| SocketIO
  SocketIO -->|"broadcast user-connected"| Browser1
  SocketIO -->|"broadcast user-connected"| Browser2

  %% Connections: PeerJS Signaling
  Browser1 -->|"WS: PeerJS signaling"| PeerJS
  Browser2 -->|"WS: PeerJS signaling"| PeerJS

  %% P2P Media Mesh
  Browser1 ---|"WebRTC Media"| Browser2

  %% Optional External Integrations
  Express -->|"store metadata"| MongoDB
  PeerJS -->|"NAT traversal"| STUNTURN
  Express -->|"static offload"| CDN

  %% Click Events
  click roomEJS "https://github.com/cleverprogrammers/nodejs-zoom-clone/blob/master/views/room.ejs"
  click scriptJS "https://github.com/cleverprogrammers/nodejs-zoom-clone/blob/master/public/script.js"
  click styleCSS "https://github.com/cleverprogrammers/nodejs-zoom-clone/blob/master/public/style.css"
  click Express "https://github.com/cleverprogrammers/nodejs-zoom-clone/blob/master/server.js"
  click SocketIO "https://github.com/cleverprogrammers/nodejs-zoom-clone/blob/master/server.js"
  click PeerJS "https://github.com/cleverprogrammers/nodejs-zoom-clone/blob/master/server.js"
  click packageJSON "https://github.com/cleverprogrammers/nodejs-zoom-clone/blob/master/package.json"
  click packageLock "https://github.com/cleverprogrammers/nodejs-zoom-clone/blob/master/package-lock.json"

  %% Styles
  classDef client fill:#e0f7e9,stroke:#2f8f68,color:#000
  classDef server fill:#cce5ff,stroke:#1760a5,color:#000
  classDef external fill:#ffe0b2,stroke:#a05600,color:#000
```
