How indian-meet/google_meet works
This is a microservices video-calling app. A browser uses the API Gateway for account, profile, room, and chat-history REST operations, while connecting directly to Signaling over WebSocket for live room coordination and WebRTC signaling. Signaling consults the Room Service and coordinates media through the SFU; chat messages are published through Redis for persistence by Chat Service. The README documents these service boundaries and integrations; unsampled service internals are represented only at supported directory paths.
Main entry points: proxyRoutes.ts HTTP API Gateway · index.ts WebSocket signaling · loginController.ts Accounts and tokens · getMessagesController.ts Chat history API
Components 15
Client edge
- HTTP API Gateway
services/api-gateway/src/routes/proxyRoutes.ts - STUN/TURN
Identity and profiles
- Accounts and tokens
services/auth-service/src/controllers/loginController.ts - Auth PostgreSQL
services/auth-service/src/config/db.ts - User profiles
services/user-service/src/controllers/updateProfileController.ts - User PostgreSQL
services/user-service/src/config/db.ts
Rooms and chat
- Room lifecycle
services/room-service/src/controllers/endRoomController.ts - Room PostgreSQL
services/room-service/src/config/db.ts - Chat history API
services/chat-service/src/controllers/getMessagesController.ts - Chat MongoDB
services/chat-service/src/models/ChatMessage.ts
Live media
- WebSocket signaling
services/signaling-service/src/socket/index.ts - Redis presence and events
services/signaling-service/src/config/redis.ts - WebRTC media SFU
services/sfu-service/src/controllers/transportController.ts - Media room state
services/sfu-service/src/mediasoup/peerManager.ts
Other components
- Browser client
Connections 18
- Browser client → HTTP API Gateway: sends REST
- HTTP API Gateway → Accounts and tokens: proxies auth
services/api-gateway/src/routes/proxyRoutes.ts - HTTP API Gateway → User profiles: proxies profiles
services/api-gateway/src/routes/proxyRoutes.ts - HTTP API Gateway → Room lifecycle: proxies rooms
services/api-gateway/src/routes/proxyRoutes.ts - HTTP API Gateway → Chat history API: proxies history
services/api-gateway/src/routes/proxyRoutes.ts - Accounts and tokens → Auth PostgreSQL: reads and writes
services/auth-service/src/controllers/loginController.ts - Accounts and tokens → STUN/TURN: issues credentials
- Browser client → STUN/TURN: uses ICE
- User profiles → User PostgreSQL: reads and writes
services/user-service/src/controllers/updateProfileController.ts - Room lifecycle → Room PostgreSQL: reads and writes
services/room-service/src/controllers/endRoomController.ts - Browser client → WebSocket signaling: connects WebSocket
- WebSocket signaling → Room lifecycle: fetches room
- WebSocket signaling → Redis presence and events: tracks presence
- WebSocket signaling → WebRTC media SFU: coordinates media
- WebRTC media SFU → Media room state: manages peers
services/sfu-service/src/controllers/transportController.ts - WebSocket signaling → Redis presence and events: publishes chat events
- Chat history API → Redis presence and events: subscribes events
- Chat history API → Chat MongoDB: reads history
services/chat-service/src/controllers/getMessagesController.ts