Real Time Updates easy
Server-Sent Events (SSE) are ideal for which type of real-time application?
- A A multiplayer first-person shooter game.
- B A video chat app.
- C A live stock ticker or sports score feed (One-way updates from Server to Client).
- D A file upload service.
Answer: C. A live stock ticker or sports score feed (One-way updates from Server to Client).
SSE is a one-way channel. The server can push updates to the client, but the client cannot push back over the same channel. This is perfect for 'ReadOnly' feeds like scores or stocks.
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'?
- What is the primary advantage of using a WebSocket over standard HTTP for a chat application?