HTTP Long Polling vs Server Sent Events vs Websockets | Tech Primers

  Рет қаралды 21,634

Tech Primers

Tech Primers

Күн бұрын

Пікірлер: 26
@saurabh9446
@saurabh9446 Жыл бұрын
Freaking loving this channel 🔥 we'll be waiting from now for the new chapter 😂
@TechPrimers
@TechPrimers Жыл бұрын
🫡
@saurabh9446
@saurabh9446 Жыл бұрын
@@TechPrimers any chances of creating nodejs/golang examples for the theory being discussed
@vivi-dj7oo
@vivi-dj7oo Жыл бұрын
Thank you for this video! The explanation was very clear and helpful. :)
@TechPrimers
@TechPrimers Жыл бұрын
Glad it was helpful!
@pedronunes9043
@pedronunes9043 Жыл бұрын
Thank you! This was very clarifying.
@DebopriyoBasu
@DebopriyoBasu 8 ай бұрын
Amazing explanation! The examples really helped me reinforce my understanding.
@hkkabir2024
@hkkabir2024 Жыл бұрын
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
@ghoulbond
@ghoulbond Жыл бұрын
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.
@sergeibatiuk3468
@sergeibatiuk3468 11 ай бұрын
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?
@ranuchir
@ranuchir 9 ай бұрын
How and where is the user session maintained for SSE and Web sockets? Please share
@sertunc-k5o
@sertunc-k5o Жыл бұрын
under hige load which should we use ? websocket vs long polling ? thank you
@girishanker3796
@girishanker3796 10 ай бұрын
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.
@J1MKAKA1N
@J1MKAKA1N 9 ай бұрын
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.
@TheKennyWorld
@TheKennyWorld Жыл бұрын
Very detailed and clear explanation
@TechPrimers
@TechPrimers Жыл бұрын
Glad it was helpful!
@ayyanarjayabalan
@ayyanarjayabalan Жыл бұрын
Love it. Waiting for implementation of SSE like zerodha trading application.
@TechPrimers
@TechPrimers Жыл бұрын
Done Ayyanar. Check my latest video
@EjazKhan-tr6vt
@EjazKhan-tr6vt 8 ай бұрын
Too good, easy-peasy👍
@SharmilaD-y2g
@SharmilaD-y2g Жыл бұрын
Useful session, please post session on resiliency
@連文瑞-o5n
@連文瑞-o5n 7 ай бұрын
Awesome content
@rathnakumar731
@rathnakumar731 Жыл бұрын
Mass
@JaNaMSoNi
@JaNaMSoNi Жыл бұрын
3 minutes late
@TechPrimers
@TechPrimers Жыл бұрын
oops. you can see the chapter timestamps now and navigate
@EldenNoob-yv9ke
@EldenNoob-yv9ke 8 ай бұрын
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.
Hilarious FAKE TONGUE Prank by WEDNESDAY😏🖤
0:39
La La Life Shorts
Рет қаралды 44 МЛН
Server-Sent Events Crash Course
29:48
Hussein Nasser
Рет қаралды 99 М.
HTTP Polling vs SSE vs WebSocket vs WebHooks
22:22
ByteVigor
Рет қаралды 15 М.
HTTP 1 Vs HTTP 2 Vs HTTP 3!
7:37
ByteByteGo
Рет қаралды 347 М.
I Wrote HTTP "From Scratch" (It Was Easy)
19:07
Sean Bix
Рет қаралды 88 М.