WebHooks: Good for updating clients on certain events and avoiding pulling style endpoints WebSockets: Good for low latency two-way communications HTTP Streaming: Good for long-term connections over HTTP
@@Zen-t2j WebHook is more indicated if you need a bi-directional fast communication (eg: a shooter online game). In your case of social app, your cliente just need to receive new messages, so might be better if you use streaming. For things like chat messages, I would said that the better options should be use something like MQTT. You can also do it by using Long Pooling, but it can be quite inefficient
I’m glad you liked the explanation! Thanks for the feedback, it’s very valuable to me. I’ll definitely keep the background music in mind for future videos 👌
@@ambientcoder5462 the music genre is perfect and for any other video format than information/explanation /education the volume is too but here as the comment said just a smidge too loud. Have agreat day!
Keeping a long-living connection is another issue with WebSocket if you use a cloud platform like Cloudflare for DDoS protection. Long-living connections cause Cloudflare servers to run out of ports, so the company has to take fee for that.
Yup you’re right. If there isn’t much traffic, websockets might be overkill. If you’d still like to keep things event driven, then webhooks might be an option worth considering.
This is so helpful. Thank you so much. It would be great if you could also provide the source of this information, books or articles that you referred to in order to put this together.
Hi, it is a very good presentation. It is very helpful. If my application is very complex where it need to handle "Request-Response" and "Event-driven" API, how to define and aggregate both this API's?
Your API will contain multiple endpoints. So each endpoint can be a different style of endpoint depending on your use case. For example, retrieving a list of videos on a server is a request-response style endpoint. However, to stream an individual video would not necessarily be request-response style endpoint. It is important that you document these traits to the end user. Hope this helps 🙂
Hi, which technique were used in push notification, like when someone replied our comment, and we get a notified in the inbox area with the amount of replies we are getting? like the bell icon in youtube
Hey Gaurav, basically it depends on the API. For example, websockets require both the client and server to establish a websockets connection. Hope this helps! 🙂
I've cleared explained why it's inefficient. Of course I have not gone into deep details but I've covered as much as I can in a short video. How exactly am I misinforming people?
@@ambientcoder5462 A frequent request isn't a cause of the slowness. I appreciate your attempt to educate people, but before doing that, you need have a clear understanding for yourself.
![[#2024MAMA] BIGBANG (빅뱅) - 뱅뱅뱅 (BANG BANG BANG) + FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/EQsYfiPR9uM/mqdefault.jpg)
WebHooks: Good for updating clients on certain events and avoiding pulling style endpoints
WebSockets: Good for low latency two-way communications
HTTP Streaming: Good for long-term connections over HTTP
I assume HTTP streaming would be optimal for updating notifications for a social app? Or would that be a WebHook?
@@Zen-t2j WebHook is more indicated if you need a bi-directional fast communication (eg: a shooter online game). In your case of social app, your cliente just need to receive new messages, so might be better if you use streaming.
For things like chat messages, I would said that the better options should be use something like MQTT. You can also do it by using Long Pooling, but it can be quite inefficient
Man, I just came across your channel and its very sad that you stopped for a year now. The way you explaining things is spot on.
Good explanation! One request, please keep the background music on a lower note (/volume) since it is causing hindrance in concentration and hearing.
I’m glad you liked the explanation! Thanks for the feedback, it’s very valuable to me. I’ll definitely keep the background music in mind for future videos 👌
Hi bro can you help me how to create webhooks for springboot microservices
@@ambientcoder5462 the music genre is perfect and for any other video format than information/explanation /education the volume is too but here as the comment said just a smidge too loud. Have agreat day!
@@ambientcoder5462 I assume HHTP streaming would be optimal for updating notifications for a social app? Or would that be a WebHook?
Great comparison video. The connection graphics, pro/con format is well done. Thanks for sharing your knowledge.
Thanks for the kind words 🙂
One of the best youtube channels explaining APIs
Thanks for the kind words! Hope you’re enjoying the content 🙂
truly an amazing video, especially since you also reviewed the Request/response at the beginning!
Thank you :)
Great explanation. I appreciate the comparison of the 3 methods with visualizations. Thanks for sharing!
Thank you :) I’m glad you liked the visualizations.
Your channel deserve 400K subscribers. let's make it to 10K first. Really clear explanation to none engineer. Hope you make more videos.
Thanks for your kind words, really appreciate them 🙂
Very clean and clear one! Thank you!!
Thank you 🙂
You are such a great teacher, I like the simplicity in the explanation 🎉 🎉 🎉 🎉 🎉 🎉 🎉
Thanks a lot! I’m glad you liked my explanations 🙂
Very helpful. Gold worth information at one place. Thanks for sharing.. really appreciate
great explanation! I haven't seen the webhooks implementation on the client-side yet, now I need to try!
Thanks!
Keeping a long-living connection is another issue with WebSocket if you use a cloud platform like Cloudflare for DDoS protection. Long-living connections cause Cloudflare servers to run out of ports, so the company has to take fee for that.
Is a con of the websocket approach that if there isn't that much traffic, it's a wasted thread keeping the connection open?
Yup you’re right. If there isn’t much traffic, websockets might be overkill. If you’d still like to keep things event driven, then webhooks might be an option worth considering.
Thanks for the informative video! It is a great help in my process of creating an application.
Glad it was helpful!
Thank you very much. That is a neat and smooth explanation. It helped me.
Happy to hear it helped you Suresh! And thanks for your kind words 🙂
Great explanation! Thanks for sharing!
Glad you enjoyed it!
This is so helpful. Thank you so much. It would be great if you could also provide the source of this information, books or articles that you referred to in order to put this together.
Does MPEG DASH use http streaming under the hood or websockets for streaming videos?
Most, if not all, video streaming platforms use HTTP streaming as far as I know. Hope this helps!
Thanks for crystal clear explanation
I’m glad you liked the explanation. Thanks for your support 🙂
Thank you. Very informative.
Subscribed!
Appreciate the support! 🙂
Clear and concise explanation. Thank you!
Thanks Johnny 🙂
Hi, it is a very good presentation. It is very helpful. If my application is very complex where it need to handle "Request-Response" and "Event-driven" API, how to define and aggregate both this API's?
Your API will contain multiple endpoints. So each endpoint can be a different style of endpoint depending on your use case.
For example, retrieving a list of videos on a server is a request-response style endpoint. However, to stream an individual video would not necessarily be request-response style endpoint.
It is important that you document these traits to the end user.
Hope this helps 🙂
Great video, brief, to the point.. Thanks!
This was perfect. Thank you so much.
Great video, thanks!
Thanks! 🙂
Great content. Very enlighting.
you're very good at explaining the concepts. thanks.
Glad you think so!
Nice video. Informative and to the point without any fluff 👍🏼
Thank you!
Hi, which technique were used in push notification, like when someone replied our comment, and we get a notified in the inbox area with the amount of replies we are getting? like the bell icon in youtube
Very useful, thank you!
What about the GraphQL subscriptions? 🤔
Amazing explanation 👍
I’m glad you liked it! Thanks for your kind words :)
Great video!
Thank you! 🙂
In webhooks, the client is actually another api server, which exposes an end point rather than a mobile or web client, is that correct?
Where does pub-sub with for example MQTT fall under?
Can you show how to make a secure node js running from php cli that uses cert an key pem files that allow voice streaming 2 way like a phone call app?
Thanks for the suggestion, I’ll consider it 🙂
Real good
Thank you
Thank you!
Great explanation!
Thanks Jemil 🙂
Excellent !!!
Just what I needed 😃
Perfect!!!
i still don't follow webhooks but other two were crystal clear
Thanks 🙂
you as client need to provide an public endpoint which the server can call when a certain (by the user/client) specfied event occurs.
You need to put your contact info in the TH-cam about section.
Thanks for pointing this out Steven. I've updated the about section with my channel contact :)
Great explanation.
Thanks 🙂
nice man!
Thanks bro! 🙂
Good overview, thanks
Can i send an http post request while streaming over http?
Thanks!
Thanks for your sharing
This is useful information
greatttttt video
anyone here..
my question is can we use any of these connection type to any Api or it depends on Api.
Hey Gaurav, basically it depends on the API. For example, websockets require both the client and server to establish a websockets connection.
Hope this helps! 🙂
When did http become event driven?
well done thanks! :)
Great
Thank you
Thanks.
Thank a lot man❤Happy that I found your channel
great video but music is distracting
Website socket is best
Why not SSE
🏆🇮🇩
The music in the background is really disturbing and distracting
Thanks for the feedback. I'll keep that in mind for future videos
🎶 music is weird.
put speed 1.5.. you welcome 😉
Just remove that background music.... Its annoying
No, no, again you explain not right. You do not explain why it is inefficient. Oh boy, misinforming people is really bad.
I've cleared explained why it's inefficient. Of course I have not gone into deep details but I've covered as much as I can in a short video. How exactly am I misinforming people?
@@ambientcoder5462 A frequent request isn't a cause of the slowness. I appreciate your attempt to educate people, but before doing that, you need have a clear understanding for yourself.
Thanks!