[00:02] 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
[00:18] 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
[00:32] 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
[00:46] 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.
[01:00] 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
[01:13] time updates pattern on Hello Interview and follow us for more system design.