What Is a Server

A server is a computer whose job is to wait for requests from other computers and answer them — the word names a role, not a special kind of machine, so the same hardware the first topic described becomes a server simply by running a program that listens for requests and responds, exactly the counterpart to the client that the internet, email, and web-browser topics kept mentioning. The relationship is called client-server: the client is the computer that asks (your phone, your laptop, your browser) and the server is the computer that answers, and almost everything you do online is some version of this exchange — a browser asks a web server for a page, an email program asks a mail server for new messages, an app asks its backend server for your data. What makes a machine a server is therefore behavior, not appearance: an old laptop running a program that listens for requests is a server, while a giant machine doing no listening is not. That said, computers built specifically to be servers are usually optimized for the role: they are designed to run continuously without being switched off, to handle many requests at the same time, and to keep going when parts fail — which is why they often have duplicated power supplies and drives, and why they live in the climate-controlled data centers the cloud topic described rather than on a desk. A single physical server almost never does just one thing; through a technique called virtualization it can be split into many virtual servers that each behave like an independent machine, which is exactly what a cloud provider rents out when you "rent a server" without ever touching real hardware. Servers are also specialized by what they serve: a web server sends web pages, a database server (hosting the kind of database its own topic covered) stores and retrieves structured data, a file server holds shared files, and a mail server handles email — and a single real app usually relies on several of these working together behind the scenes. Because a server answers requests from anyone who can reach it over the network, two concerns from earlier topics apply with full force: security, since a server exposed to the internet is constantly probed by attackers and must be carefully locked down the way the staying-safe-online topic described, and capacity, since a server can only handle so many simultaneous requests before it slows or fails, which is why busy services run many servers behind a load balancer that spreads incoming requests across them. The simple takeaway is that a server is not mysterious: it is an ordinary computer playing the role of the answerer in a conversation, kept running and reachable so that clients everywhere can ask it for something and reliably get a response.

Client
the computer that asks — your phone, laptop, or browser
Request over the network
"please send me this page / my messages / my data"
Server
a computer running a program that listens and answers, kept always on
Web server
sends pages
Database server
stores and retrieves data
Mail server
handles email
File server
holds shared files
Client Asks, Server Answers "server" is a role in a conversation, not a special kind of machine Client phone, laptop, browser the one that asks Server listens and answers kept always on request response the same hardware becomes a server just by running a program that listens; an old laptop can be a server, and many clients can share one server
One Busy Service, Many Servers a load balancer spreads requests so no single server is overwhelmed many clients all asking at once Load balancer spreads the requests server 1 server 2 server 3 add more servers to handle more clients — the core idea behind scaling a service

Take what is a server further

Ask the copilot about this term, or have our engineers assess it against your process.