In my opinion, server-sent event would be the ideal choice for this scenario, I recently used server-sent events in one of project for live notifications service, alongside this you can make use of RabbitMQ or Kafka in the backend for the scalable architecture.
Long polling nowadays is almost always a bad idea. WebSockets are lighweight, fast, async, scalable, widespread and don't spam a server with requests. SSE could be useful for some specific cases, but it's hard to scale.
useless and incorrect video. 1. No info on TCP connection like is the same connection is reused. 2. SSE is used for communicating textual data and not binary data like video streaming.
Amazing explanation! The examples really helped me reinforce my understanding.
Thank you! This was very clarifying.
Freaking loving this channel 🔥 we'll be waiting from now for the new chapter 😂
🫡
@@TechPrimers any chances of creating nodejs/golang examples for the theory being discussed
Thank you for this video! The explanation was very clear and helpful. :)
Glad it was helpful!
Very detailed and clear explanation
Glad it was helpful!
Awesome content
Too good, easy-peasy👍
Love it. Waiting for implementation of SSE like zerodha trading application.
Done Ayyanar. Check my latest video
Useful session, please post session on resiliency
Mass
what is the best way for implementing notification for huge amount of data? i feel very comfortable with long pooling . plz give me your opinion
In my opinion, server-sent event would be the ideal choice for this scenario, I recently used server-sent events in one of project for live notifications service, alongside this you can make use of RabbitMQ or Kafka in the backend for the scalable architecture.
How and where is the user session maintained for SSE and Web sockets? Please share
Is threading on a server going to be an issue with long polling / server sent events if the server is non-blocking, like webflux or scala http4s?
under hige load which should we use ? websocket vs long polling ? thank you
Long polling🤔 coz we can't horizontally scale web sockets since they are stateful and also long polling provides enough delay at the server side.
Long polling nowadays is almost always a bad idea. WebSockets are lighweight, fast, async, scalable, widespread and don't spam a server with requests. SSE could be useful for some specific cases, but it's hard to scale.
3 minutes late
oops. you can see the chapter timestamps now and navigate
useless and incorrect video.
1. No info on TCP connection like is the same connection is reused.
2. SSE is used for communicating textual data and not binary data like video streaming.