Do I use REST or Socket.io for chat?
Both. Use REST for loading message history (GET /chat/:userId with pagination) and chat list. Use Socket.io for real-time events (new messages, typing indicators, online status). REST handles initial load, Socket.io handles live updates.
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in Building a Real-Time Live Chat Feature Overview and Architecture
Backend: Message model (MongoDB), Socket.io server, chat REST API, socket events (message:send, message:received, typing), JWT auth, room management. Frontend: chat list, chat window, message input, typing indicator, online status, unread badge.
User A sends a message via Socket.io emit, server saves to MongoDB, server broadcasts to the room, User B receives instantly via Socket.io. If User B is offline, server sends an email notification. Message history is loaded via REST API when opening a chat.
Real-time messaging, message persistence (saved to database), message history (load old messages with pagination), typing indicators, online/offline status, message read receipts, unread message count, and notifications for offline users.
Still have questions?
Browse all our FAQs or reach out to our support team