How 58tinkal/chatt_app works
Project Type & Purpose
• This is a full-stack MERN chat application with real-time messaging, user authentication (JWT), one-to-one and group chats, built-in Socket.io.
• Frontend: React + Chakra UI, state via React Context, communicates over REST and WebSockets.
• Backend: Node.js + Express + Mongoose, exposes REST endpoints under /api/user, /api/chat, /api/message, and hosts a Socket.io real-time layer.
• Database: MongoDB (via Mongoose) for users, chats, messages.
High-Level File Structure & Architectural Patterns
• Root
• package.json – scripts to start backend (npm start), build frontend (npm run build).
• /backend
• config/ – DB connection (db.js), JWT token generator (generateToken.js)
• middleware/ – auth (JWT validation), error handlers
• models/ – Mongoose schemas (User, Chat, Message)
• controllers/ – business logic for users, chats, messages
• routes/ – Express routers mounted on /api/*
• server.js – Express app bootstrapping, Socket.io initialization
• /frontend
• public/ – static HTML, manifest, robots.txt
• src/ – React entry (index.js), App.js (Router), Context (ChatProvider), Pages (Homepage, Chatpage), UI components (Chatbox, SideDrawer, modals), config utilities, sample data.
• build/ & dist/ – production bundles
• Patterns
• Layered architecture (Presentation → Business Logic → Data Access)
• Context for global state
• REST + WebSocket hybrid
Main Components & Their Interactions
• Client Browser (React SPA)
• Sends HTTP(S) requests to Express API (user auth, fetch chats/messages)
• Opens WebSocket connection to Socket.io server for real-time events (typing, newMessage)
• Express Server
• REST layer: userRoutes, chatRoutes, messageRoutes → controllers → models → MongoDB
• Socket.io layer: listens for client events, emits updates to relevant sockets
• JWT middleware: secures REST endpoints
• MongoDB
• Collections: users, chats, messages
• Mongoose ORM handles schema & population of references
• External Services
• Browser localStorage (persists JWT)
• Potential future: file storage, push notifications
Architectural Patterns & Design Principles
• Separation of concerns: UI, service layer, data layer
• Single Page Application assisted by React Router
• Real-time pub/sub via WebSockets (Socket.io)
• Token-based authentication (JWT)
• MVC-style on backend (Routes → Controllers → Models)