How fmeringdal/nettu-meet works
And group the main components
• Frontend Application
– React/TypeScript SPA
– Served via Nginx in Docker
– Feature modules: account, chat, canvas (whiteboard), media manager, meeting flow, file upload, graph plotter
• Backend API Server
– Node.js/TypeScript Express (HTTP + WebSocket)
– Clean architecture layers: HTTP controllers → DTOs → Use-Case interactors → Domain models → Repositories (Mongo implementations)
– Mediasoup SFU service for real-time media routing
– Integrations: MongoDB (persistent storage), Redis (signaling, session), optional email and file-storage services
• Infrastructure
– Docker Compose orchestration (MongoDB, Redis, server container, frontend container)
– CI/CD workflows (.github/workflows)
• External/Third-Party Services
– Email provider (SMTP)
– Storage (for uploaded files)
– Swagger for API docs
Relationships and data flows
• User’s Browser ↔ Nginx ↔ React SPA
• React SPA → HTTP REST calls → Express API (e.g., account creation, meeting management, chat history)
• React SPA ↔ WebSocket → Express WebSocket endpoints for chat signaling, canvas updates
• React SPA ↔ WebRTC (via client-side MediaManager and PeersManager) → Mediasoup SFU (deployed within the server container) for audio/video streams
• Express Use-Cases → MongoDB (via mongo…Repo implementations) for persisting users, meetings, canvas data, chat logs
• Signaling messages for WebRTC routed via Redis pub/sub
• Email-verification flows: UseCase → email service → user’s mailbox
Architectural patterns and principles
• Clean/Hexagonal architecture in server: isolates business rules (Use-Cases) from HTTP and DB details
• Feature-based modular structure in frontend: each module encapsulates components, services, state, interactors
• Single SPA served behind Nginx for caching/static assets
• Docker for environment consistency; CI/CD workflows automate builds