When you open a website, you're asking a computer somewhere to send it to you. That computer is a server.
Picture a waiter who never goes home. Someone can walk in at any hour and order. The waiter brings exactly what was asked for.
A server is that waiter for the internet. It’s a computer that stays switched on all the time, waiting for requests and serving answers: web pages, photos, emails, videos.
Who’s asking
- your browser asks for a web page
- your phone asks for new messages
- another app asks for some data through an API
The device asking is often called the client. The client asks. The server answers.
Where servers live
Most sit in huge buildings called data centres, packed with rows of machines that have strong cooling, backup power and fast internet. Renting space on someone else’s servers is what people mean by the cloud.
What it isn’t
It isn’t a special kind of magic box. A server is a computer much like yours, just set up to run all day without a screen and to answer many people at once.
Where the comparison breaks down
A waiter serves one table at a time. A busy server answers thousands of requests every second, from all over the world.
How the words fit together
The backend runs on a server. Hosting means renting a server for your website. The cloud is renting servers by the hour.
“Server” can mean the physical machine or just the program on it that answers requests. One machine can run many servers.

When you'll hear it
“The server is down.” The computer that sends the website isn't answering, so nobody can load it.
“It's a server-side problem.” The issue is on their computers, not on your phone or laptop.
“We need a bigger server.” The current computer can't keep up with how many people are using it.
“If our server went down tonight, who would find out first and how?”

Try it yourselfReady to use it? The exact commands are on my other site, devcmds: Run a local web server ↗


