WebSockets upgrade an HTTP connection into a long-lived duplex channel. The browser and the server can both push without waiting to be asked — useful when the page should feel alive.
In plain language
On the web, this term comes up when people talk about how pages, apps, and services are built or connected. WebSockets upgrade an HTTP connection into a long-lived duplex channel. The browser and the server can both push without waiting to be asked — useful when the page should feel alive. If you are new to the field, the simplest mental model is this: a persistent two-way pipe over http. Read it once with that frame in mind, then come back and read it again — that is usually enough for the rest of the entry to make sense.
An everyday picture
Think of WebSocket as part of the doorway between a person and a machine. People see the door — the page that loads, the button that responds — and barely notice the hinges. WebSocket is one of the hinges.
Where it shows up
You meet WebSocket in almost every website, app, and dashboard. The piece itself is invisible; what you notice is the page that loads, the field that updates, the screen that fits the phone in your hand.
A small example
Imagine the scene above. The role WebSocket plays is the one its blurb describes — A persistent two-way pipe over HTTP. Every time a page loads or a button fires a request, ideas like this are quietly doing the work between the browser and the server.
Common misunderstanding
One line to take with you
WebSocket is part of the surface between people and machines. The user sees the result, never the seam.