---
title: '4 Ways to Push Real-Time Updates to Clients'
source: 'https://youtube.com/watch?v=38IqoJd7j5E'
video_id: '38IqoJd7j5E'
date: 2026-08-04
duration_sec: 80
---

# 4 Ways to Push Real-Time Updates to Clients

> Source: [4 Ways to Push Real-Time Updates to Clients](https://youtube.com/watch?v=38IqoJd7j5E)

## Summary

The video explains four methods for pushing real-time updates to web clients: short polling, long polling, server-sent events (SSE), and web sockets. It highlights the trade-offs of each and emphasizes that SSE is often overlooked despite being sufficient for many use cases.

### Key Points

- **Short Polling** [00:02] — Client asks the server every n seconds for updates. Simple but wasteful and can cause latency.
- **Long Polling** [00:18] — Client asks, server holds connection open until data is available, then responds. Better than polling but not ideal for high-frequency updates.
- **Server-Sent Events (SSE)** [00:32] — Server opens a one-way stream to the client over HTTP. Perfect for scenarios like live comments where clients mostly receive data.
- **Web Sockets** [00:46] — Enables continuous two-way communication, ideal for multiplayer games or terminal emulators.
- **SSE is Underrated** [01:00] — SSE often provides sufficient low latency, and you can use POST/PUT for writes. Recommended for many real-time update patterns.

### Conclusion

Choose the real-time update method based on your use case: polling for simplicity, SSE for one-way streams, and web sockets for full-duplex communication. SSE is often the best balance of simplicity and performance.

## Transcript

data to web clients and you don't need web sockets for everything. Start with short polling. The client asks the server every n seconds, anything new? everywhere, but it's wasteful and it can cause latency for your clients. Long
polling is where the client asks and the server holds the connection open until there's data and then responds. It's better than polling and it works over infrastructure. But it's not great for high frequency
updates that really need to churn. Next are server sent events. For these the server opens a one-way stream to the client over HTTP. This is perfect for applications like Facebook live comments where viewers are almost exclusively
receiving a deluge of comments, but they're only sending a few. Finally, we have web sockets. You'll use them when you need both sides to be able to talk continuously at the same time like a multiplayer game or a terminal emulator.
SSE is the standout that a lot of engineers gloss over. In most cases it gives you the low latency you need and you can make a post or a put when you need to write. Read more in our real time updates pattern on Hello Interview
time updates pattern on Hello Interview and follow us for more system design.