Looking to create a REST API or setup Websockets using AWS? Check out these step by step walkthrough videos below: REST API on API Gateway - th-cam.com/video/uFsaiEhr1zs/w-d-xo.html Websockets on API Gateway - th-cam.com/video/FIrzkt7kH80/w-d-xo.html
Lets hope someday majority of tech presenters on youtube would know how to a make a to-the-point great video - like this one. No bs, no mumbo jumbo, no need to market the channel or request for subscription etc.; just focusing on bringing the concepts home. Great job, man.
TH-camrs statistically get more subs and likes when they ask for them. You’re taking for granted how much effort goes into making videos. Why shouldn’t they try to maximize their income?
@@cyberchef8344 I too don't spend time asking for likes or subs on my channel. This is my mindset: "Make a video so good that when someone watches it, they feel like the urge to like it and then subscribe for more such content". If you don't make someone feel that, then maybe you have to improve yourself. But yes, this is just my opinion.
@@fastorial that’s definitely a good mindset to have, but at the end of the day it just boils down to trying to make the best quality videos you can. You should absolutely do that because that’s the main factor in growing an audience. With that being said, you can do that and still ask for a like or subscription. It’s not like that takes up much time. Plus, sometimes people watching videos just don’t even think about liking it. It’s not really a priority. Asking for likes has been shown statistically to produce more results. I’m not saying you have to do this, but it really is one of those situations where there is no reason not to.
The client still has to play *ping-pong* with the server to keep the connection alive, but it's safe to say, that a lot of overhead - especially the HTTP-Header - are cut out by websockets and it's my go to for web applications. In my view the REST model is still important, especially for static sites and APIs, which don't depend on near real time communication. Overall, you've done a pretty good video, it's a great explanation for newbies ^_^
Recently I had to rewrite backend of my online game from REST API to a websocket. The problem is this game was my college project and something completely amateur. But I thought I could make things more efficent by fixing the backend. By switching to websocket from rest api, average ping dropped to 30 from 100, which seemed fine. But still I had the client side playing ping-pong thing with the server, which reduces the performance of the server extremely high with each player being online. After learning more about websockets, I realised that I have to change whole logic of my communication structcure. I just removed the old system completely and switched to the websocket, I hope I will be able to implement a new structcure that is efficent for the use of the websocket. Thanks for the video and all the information.
I'm building an online game too. But it's ludo's instead. So it's like chess, but with 4 people max. I'm thinking of using websockets too, because it's a real time app, and should be as fast as possible to present better player experience. I'm using django-postgresql. Maybe I should use node js instead, but I hate javascript.
This is a cool explaining video about the usage of each... In real life you usually use both in the same application. In my case, I had to build a REST service API with some endpoints, but there is a particular Endpoint that creates a user instance for remote execution, so N users in a project can start an engine in their PC and making a GET call to the endpoint 'url/tasks/SRS' will see how many remote execution nodes are available for the project, make a direct connection between the client and a user engine with websockets and start making a remote execution and see the stdout in real time... This is very useful when having a very heavy software that requires multiple instances to run modules or subprocesses of the main one :D!
Ok so why do you have the REST API then? I understand that one of your endpoints from service API is creating an instance (websocket technique). But what other calls do the users make for the remote execution? Greetings from germany
It is good to note that the web sockets opens the connection across all the network components between the device and server. Components such as NAT will prevent the server from sending a message directly to the device without the web socket.
Good video explaining the differences and going into detail with long vs short polling. However, for this setup I would say even sockets is a bit of an outdated way of doing things. WebRTC would be the prefered method where messages are peer to peer which would only require a server for the initial peer to peer connection setup and then all messages bypass the server. Obviously depends on use case - do you need to store messages in a DB for later etc. but for a simple chat system that doesn't need stored history I would say webRTC would be the way to do this.
I like the example , i just don't understand why in the Rest case would you be waiting for the delay to update the messages when you could use the Publisher/Subscriber or the Observer pattern and then you would be updated everytime a new message is sent automatically , this way you would not waste resources making get requests all the time and you would not have the delay of the messages
Totally agree! I was looking for this comment! Additionally, I don’t see any problems with initiating new instance of the chat on receiving side (Mary in example), server should just create it for her and push messages to it. Also, this patterns are great way to handle group chats!
When you want to implemention offline messages on websockets, you will start miss the REST or HTTP things, such as cache, compress etc. Websockets is a low level transfer layer on the web, i don't think it is comparable with REST, we need a standard application protocol up on websockets, otherwise we should build it by ourself.
REST is an architecture, websocket is a transport. How can you make a comparison? Even RESTful is just an API that uses REST constraints. I would understand if you compare HTTP vs WebSocket.
Nice vídeo, just a little improvement for the next ones. You passed in about 5 minutes in rest API topic and two minutes about the web sockets. Try to balance it as much as possible.
Seems like it doesn't have to be REST vs. websocket. They had chat based on cgi in the 2000s that was very similar to your long-poll rest example, except you don't keep calling it, just have structured messages that you output as required.
It's funny how the whole "web world" which is considered "high tech" is decades behind regular programming world, sockets are something only now get wide spread support (new).. wow.. along with "typescript".. welcome to the 80s..
Ye jest, but it’s actually rather impressive. The web is now being used for things far beyond what was intended when the original protocols were designed.
Could you please recommend for me a book that's touch kinda of the important concepts necessary for backend engineer , or something like that Thank you your videos are awesome
is there a way to use websockets and rest endpoints? I have 2 clients who connect via websockets and 2 who are making api calls. I cant use socketio because of the handshake with the websocket clients. My clients expect a server hosted on ws://IP:port. My Socketio server uses http and later after deployment https. Which is fine for the api clients as i can define endpoints with flask socketio. But the websocket clients cannot connect. And I cannot host 2 servers either after deployment. Any options I have in python?
I use dyndns and want to use websockets on a small esp32 at home. I can connect from anywhere remote but not with websockets. Any help would be so appreciated.
how about using a lighter-weight tool that lets the server signal clients to do the restful api update instead of using socket to pass the actual information
Actually I think the idea of this video it was to show why you shouldn't use Rest API in this type of apps and why web sockets work better in this case
why can't you do a REST API, but have the client application own a small api as well? And then when the server has an update to give to the client, the server can do a POST call to the client.
Primarily because that would violate the entire client-server model. Like if you're going to do anything like that, then whatever you're implementing on the client side isn't an API, and realistically you're probably just making a bad homebrew equivalent of websockets. And on a practical level, the server would have to be able to initiate connections with John and Mary. That would require John and Mary to each have their own publicly-accessible URI, which for normal home users is a terrible idea and thankfully very rare.
For continuous-ish realtime communication like this, yeah sure sockets make way more sense than REST. For other applications, not so much. I've spent quite a bit of my career developing and consuming REST APIs though, and I can confirm that in a lot of cases they make /way/ more sense than anything socket-based. REST just looks bad here because, in order to make a direct comparison, this video had to use an example where REST doesn't make much sense. REST APIs are everywhere, seriously, and almost none of them could usefully be replaced by sockets.
Looking to create a REST API or setup Websockets using AWS? Check out these step by step walkthrough videos below:
REST API on API Gateway - th-cam.com/video/uFsaiEhr1zs/w-d-xo.html
Websockets on API Gateway - th-cam.com/video/FIrzkt7kH80/w-d-xo.html
Lets hope someday majority of tech presenters on youtube would know how to a make a to-the-point great video - like this one. No bs, no mumbo jumbo, no need to market the channel or request for subscription etc.; just focusing on bringing the concepts home. Great job, man.
TH-camrs statistically get more subs and likes when they ask for them. You’re taking for granted how much effort goes into making videos. Why shouldn’t they try to maximize their income?
@@cyberchef8344 I too don't spend time asking for likes or subs on my channel. This is my mindset: "Make a video so good that when someone watches it, they feel like the urge to like it and then subscribe for more such content". If you don't make someone feel that, then maybe you have to improve yourself. But yes, this is just my opinion.
@@fastorial that’s definitely a good mindset to have, but at the end of the day it just boils down to trying to make the best quality videos you can. You should absolutely do that because that’s the main factor in growing an audience. With that being said, you can do that and still ask for a like or subscription. It’s not like that takes up much time. Plus, sometimes people watching videos just don’t even think about liking it. It’s not really a priority. Asking for likes has been shown statistically to produce more results. I’m not saying you have to do this, but it really is one of those situations where there is no reason not to.
The client still has to play *ping-pong* with the server to keep the connection alive, but it's safe to say, that a lot of overhead - especially the HTTP-Header - are cut out by websockets and it's my go to for web applications. In my view the REST model is still important, especially for static sites and APIs, which don't depend on near real time communication.
Overall, you've done a pretty good video, it's a great explanation for newbies ^_^
HTTP/2 solves the header overhead.
Recently I had to rewrite backend of my online game from REST API to a websocket. The problem is this game was my college project and something completely amateur. But I thought I could make things more efficent by fixing the backend. By switching to websocket from rest api, average ping dropped to 30 from 100, which seemed fine. But still I had the client side playing ping-pong thing with the server, which reduces the performance of the server extremely high with each player being online. After learning more about websockets, I realised that I have to change whole logic of my communication structcure. I just removed the old system completely and switched to the websocket, I hope I will be able to implement a new structcure that is efficent for the use of the websocket. Thanks for the video and all the information.
I'm building an online game too. But it's ludo's instead. So it's like chess, but with 4 people max. I'm thinking of using websockets too, because it's a real time app, and should be as fast as possible to present better player experience. I'm using django-postgresql. Maybe I should use node js instead, but I hate javascript.
This is a cool explaining video about the usage of each...
In real life you usually use both in the same application. In my case, I had to build a REST service API with some endpoints, but there is a particular Endpoint that creates a user instance for remote execution, so N users in a project can start an engine in their PC and making a GET call to the endpoint 'url/tasks/SRS' will see how many remote execution nodes are available for the project, make a direct connection between the client and a user engine with websockets and start making a remote execution and see the stdout in real time...
This is very useful when having a very heavy software that requires multiple instances to run modules or subprocesses of the main one :D!
Ok so why do you have the REST API then? I understand that one of your endpoints from service API is creating an instance (websocket technique).
But what other calls do the users make for the remote execution?
Greetings from germany
not saying this comment applies to this video, but miss the dislike metric. it gives a clear indication of how useful a technical video is going to be
It is good to note that the web sockets opens the connection across all the network components between the device and server. Components such as NAT will prevent the server from sending a message directly to the device without the web socket.
Good video explaining the differences and going into detail with long vs short polling. However, for this setup I would say even sockets is a bit of an outdated way of doing things. WebRTC would be the prefered method where messages are peer to peer which would only require a server for the initial peer to peer connection setup and then all messages bypass the server. Obviously depends on use case - do you need to store messages in a DB for later etc. but for a simple chat system that doesn't need stored history I would say webRTC would be the way to do this.
Very clear explanation , thanks for posting it !
Glad it was helpful!
Brilliantly explained! Need more such top level videos to deconstruct software.
Thanks!
Awesome. Your way to learn it's very clear! Thanks to share this content.
Glad it was helpful!
Thank you. A very clear and to the point presentation.
Thank you for the excellent and concise presentation of these two techniques! 👍
You're very welcome!
Very clear and simple description. Thank you very much
Excellent video. 🙏 Thanks
You're very welcome!
Love your straight forward presentation man!
Thanks Saborni!
Amazing explanation
Glad it was helpful!
Clean and simple explanation, nice job!
Awesome
Thanks!
excellent
very good clear and concise video
Man I love your videos. Please do a vid on automation using AWS if you ever find the time
Thank you so much for comming up with an excellent explaination of complex mechanisms.
You're very welcome Faraz!
Great content!
Thank you!
Beautiful explanation
Thank you!
This a clear and simple explanation of the difference between REST API and Websockets! Well done.
Crisp and straight to point 👍🏽
I like the example , i just don't understand why in the Rest case would you be waiting for the delay to update the messages when you could use the Publisher/Subscriber or the Observer pattern and then you would be updated everytime a new message is sent automatically , this way you would not waste resources making get requests all the time and you would not have the delay of the messages
Totally agree! I was looking for this comment! Additionally, I don’t see any problems with initiating new instance of the chat on receiving side (Mary in example), server should just create it for her and push messages to it. Also, this patterns are great way to handle group chats!
Thank you for the explanation.
You're very welcome!
This is a really good explanation in 7 mins. Thanks.
When you want to implemention offline messages on websockets, you will start miss the REST or HTTP things, such as cache, compress etc. Websockets is a low level transfer layer on the web, i don't think it is comparable with REST, we need a standard application protocol up on websockets, otherwise we should build it by ourself.
SignalR from Microsoft will solve that.
What is the protocol / approach used to upload say videos on TH-cam or maybe Netflix etc. Like 5 to 10 gb. Thanks
Amazing explanation..💯
Super clear! thank you
You're very welcome Christian!
this is good but you should have touched upon a little bit with the new bi-directional aspect of HTTP/2 and also on SSE.
Thanks for this video
You're very welcome!
thanks this video was really helpful
You're very welcome!
Server-Sent-Events(SSE) does the same without WebSockets
Smooth explanation
IIRC slack & whatsapp messaging both uses websockets which is why is quick.
Correct!
This might be better described as "HTTP vs Websockets".
So the connection is made once and the exchange of multiple messages happens continuously in the WebSockets concept. Right?
Did you get the idea for this video from the comment in your previous video about stock tracker?
Yes I did!
very helpful, thank you.
You're very welcome!
Great video! But does anyone else notice that the Mary and John boxes are not the same distance from the chat app box? lol my ocd is kicking in 😬
Yikes I try to align them but I guess I missed them!
so cool and easy. Please continue!
Thank you so much!!!
You're very welcome!
That was smooth!!!
REST is an architecture, websocket is a transport. How can you make a comparison? Even RESTful is just an API that uses REST constraints. I would understand if you compare HTTP vs WebSocket.
Awesome explanation. Thanks
thank you
Are John and Mary winchesters? jokes aside nice and informative video.
Nice vídeo, just a little improvement for the next ones. You passed in about 5 minutes in rest API topic and two minutes about the web sockets. Try to balance it as much as possible.
Thanks for the suggestion Thiago!
Perfect
Seems like it doesn't have to be REST vs. websocket. They had chat based on cgi in the 2000s that was very similar to your long-poll rest example, except you don't keep calling it, just have structured messages that you output as required.
tnx a loooooot❤️
Nice summary
It's funny how the whole "web world" which is considered "high tech" is decades behind regular programming world, sockets are something only now get wide spread support (new).. wow.. along with "typescript".. welcome to the 80s..
Ye jest, but it’s actually rather impressive. The web is now being used for things far beyond what was intended when the original protocols were designed.
Can you do a video on how to scale websocket?
it's not scalable by default. maybe try to mimics mmorpg architecture, using redundant nodes perhaps.
WebSockets are so underrated.
What's up with pricing? WebSockets stay opened during chat. This is better, but I have heard that you must close the services connected to WebSockets?
Amazing!
Could you please recommend for me a book that's touch kinda of the important concepts necessary for backend engineer , or something like that
Thank you your videos are awesome
This example should be on the Wikipedia page on WebSockets. Well done!
Thank you so much!
Subbed!
awesome stuff thanks
Why don't just use GraphQL Subscription in this case?
Websocket is http 2.0 native feature. REST API is http-based messaging architecture. Right?
Can you please put a video on redshift and elasticcache
is there a way to use websockets and rest endpoints? I have 2 clients who connect via websockets and 2 who are making api calls. I cant use socketio because of the handshake with the websocket clients. My clients expect a server hosted on ws://IP:port. My Socketio server uses http and later after deployment https. Which is fine for the api clients as i can define endpoints with flask socketio. But the websocket clients cannot connect. And I cannot host 2 servers either after deployment. Any options I have in python?
I use dyndns and want to use websockets on a small esp32 at home. I can connect from anywhere remote but not with websockets. Any help would be so appreciated.
Last time I looked at this, most websockets communication with end users had to use long polling under the hood. Did this change ye
how about using a lighter-weight tool that lets the server signal clients to do the restful api update instead of using socket to pass the actual information
Can someone please provide information on how to incorporate websockets in MVC architecture. Specifically how do I use websockets in controllers?
An API is a collection, not a single endpoint like /message. Use the correct terms!
Why would i use Rest APIs for such applications ? Your explanation was good, but didn't justify the title
Actually I think the idea of this video it was to show why you shouldn't use Rest API in this type of apps and why web sockets work better in this case
@@JoseDlucca that'd have made sense. Anyways, not complaining about this explanation, just felt the title should have been a little more appropriate.
@@arsive02 I agree, the title could be better
What would be that scaling concerns qith websockets?
0:30 Well for comparing wheels and squares we always want to build a bike right xD?
Great bro ,i can't understood anything 😂
why can't you do a REST API, but have the client application own a small api as well? And then when the server has an update to give to the client, the server can do a POST call to the client.
Primarily because that would violate the entire client-server model. Like if you're going to do anything like that, then whatever you're implementing on the client side isn't an API, and realistically you're probably just making a bad homebrew equivalent of websockets.
And on a practical level, the server would have to be able to initiate connections with John and Mary. That would require John and Mary to each have their own publicly-accessible URI, which for normal home users is a terrible idea and thankfully very rare.
Why is this only coming now, it seems like it is such a basic logic. Why didn’t they invented that in the 80s or 90s?
6:49 Getting popular? I thought it was getting popular about 10 years ago :)
How does one load balance websockets if the connection is stateful
Sticky sessions. Make shure the visitor stays on the same server during the entire visit.
and REST stands for ?
REpresentational State Transfer.
Compared to any socket-based protocols, the REST API looks like something broken / horribly designed. I don't understand why is still exists.
Basically it's a self-ddosing tool.
For continuous-ish realtime communication like this, yeah sure sockets make way more sense than REST. For other applications, not so much.
I've spent quite a bit of my career developing and consuming REST APIs though, and I can confirm that in a lot of cases they make /way/ more sense than anything socket-based. REST just looks bad here because, in order to make a direct comparison, this video had to use an example where REST doesn't make much sense.
REST APIs are everywhere, seriously, and almost none of them could usefully be replaced by sockets.
Sorry but chatting app seems to be an example where you need something like websockets. Nothing about comparation of architrctures
W
Push notifications
Sehr oberflächlich. Schade
Most biased example evah
Amazing explanation