Think of your computer and the servers on the internet two places connected by a highway. The method of getting something from one place to the other would be to ship it by truck.

Now, the traditional method, HTTP, would be having a one lane highway, and having the truck drive from your computer to the server, and then have the same truck drive back on the same lane.

But for WebSocket, when you just need the thing from the server as quickly as possible, you would have one lanes of a bunch of trucks going to the server, and one lane of a bunch of trucks coming back from the server, which means you’ll always be getting something back as you are send things out.

But of course, WebSocket is more complex to coordinate, since there are a lot more trucks going back and forth, so it’s good for things that needs immediate updates like chat or stock trades, but for slower things like Lemmy, it could just be simpler to keep that one lane highway.

Here is the simple napkin sized explanation.

The WebSocket protocol is a bidirectional and stateful communications protocol , unlike normal HTTP which is unidirectional and stateless . This makes WebSocket well suited for web applications such as chat programs and online gaming.

When you visit a website your browser speaks with the server in http. It is structured in requests and responses. You request a text, you get it. You request to upload an image, it is done. Very useful, but what if you wanted to get a live feed of things. Imagine you wanted to chat. You could send many requests always asking “is there a new message?” and always getting “no”. That’s not good, with a websocket your webbrowser and the server establish a live connection. Now they can send and receive small pieces of information. For chatting, games, auctions and many other things websockets are useful.