Real Time Updates easy
What is the primary advantage of using a WebSocket over standard HTTP for a chat application?
- A It encrypts the messages.
- B It enables full-duplex (bidirectional) communication, allowing the server to push messages to the client instantly without waiting for a request.
- C It uses UDP instead of TCP.
- D It allows larger file uploads.
Answer: B. It enables full-duplex (bidirectional) communication, allowing the server to push messages to the client instantly without waiting for a request.
HTTP is Request-Response (Client speaks, Server answers). WebSockets keep a pipe open so either side can speak at any time, which is essential for chat where you need to receive messages immediately.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- When a mobile app is closed/backgrounded, it cannot keep a WebSocket open. How does it receive real-time alerts (like 'New Message')?
- For a human user, what is generally considered the maximum acceptable latency for an interaction to feel 'Real-Time' (e.g., typing in a Google Doc)?
- If you want to update a news feed on a website every time a new article is published, what is the simplest (but least efficient) 'Real-Time' technique?
- In a persistent real-time connection, what is the purpose of a 'Heartbeat' or 'Ping/Pong' message?
- Why is Short Polling considered 'Chatty'?
- Server-Sent Events (SSE) are ideal for which type of real-time application?