I watched several talks from whatsapp, netflix and random articles online about how push notification works. Got a vague idea about long poll and websocket/sse. but still couldn't sort their pros & cons out clearly....until I found your channel! this is all I need. I could have saved 5 hours! Awesome work! This channel is pure gold and I'm sure people will realize it soon.
The server can have way more than 65k active connection , this limit is per IP ( user IP ) so one user can have maximum 65k open connection , but overall the server has no limit of connections , only the resources ( CPU and memory ) are the limits .
Thank you for the nice video! Quick question: in case of web socket, can we put a load balancer in front of the servers to prevent thundering herd? Why do we have to manually configure the routing?
Basically websockets are persistent while long polling isn't so they'll gradually break and reconnect meaning that they won't all be connected to the dying server at once and will be load balanced throughout whereas websockets will all try to reconnect at the same time
Just a small doubt , for a client connected to server through a web-socket, and lets say server goes down and socket connection breaks, and when server is up again the client automatically creates a socket connection , is this new socket the same as previously broken socket?If its a new socket does previous one gets garbage collected?
About server handling 65,000 active connection limit, isn't it just port 443 and can handle any number of incoming client connections, limited by system resources and the number of file descriptors available?
@@marklarization Honestly probably not as most people are only concerned with realtime updates in these interviews as they pertain to sending them from server to client.
