Does any of this sound familiar? Right after a popular game’s update, the screen says “the servers are busy.” At work, an email announces “the system will be down this weekend while we migrate the server.” The news reads out “the company’s servers were hit by a cyberattack” ── all everyday phrases. But if someone asked you, “So, what exactly is a server?”, could you explain it in your own words? Surprisingly few people can.
This article explains what a server really is, from the ground up. Here is the reveal in one line ── a server is not the name of a special kind of machine, but the name of a role: “answer when asked.” That is why, once the mechanism is set up, even an ordinary PC can become a server. And the screen you touch directly is merely a counter; behind it, there is always a headquarters that records and keeps all the information. If any of the following rings a bell, read on.
- You’ve nodded along to “the server is down” while only pretending to understand
- You have (or want) a “rental server” plan, but can’t explain what you’re actually renting
- The only image “server” brings to mind is an expensive, large computer
- You couldn’t answer if asked how web servers, mail servers, and DNS servers differ
This article avoids piling on jargon, so beginners can follow along. And it doesn’t stop at how things work: it also covers the practical question of what you can actually do when “the server is down.”
| Question | Where it’s covered |
|---|---|
| What is a server, really? | §1 |
| How is it different from an ordinary PC? | §2 |
| Web server, mail server… what’s the difference? | §3 |
| What is actually happening when “the server is down”? | §4 |
| Where are servers? What is a rental server? | §5 |
| Can my own PC become a server? | FAQ Q3 |
Starting with our series overview What Happens Between Typing a URL and the Page Appearing?, four of our articles have promised that “what a server really is deserves an article of its own.” This is that article.
1. What a Server Really Is ── the Computer That Answers When Asked
1-1. Every Day, You Send “Requests” Far Away
Opening a single page ── that casual act is really the sending of a request, “please give me this page,” to somewhere far away. The request parcel leaves your home router, travels through many relay points, and arrives at the target computer (the full journey is covered in What Happens Between Typing a URL and the Page Appearing?; there is also a gatekeeper inspecting parcels at the building’s entrance → the firewall article). The computer at the destination reads the request, prepares an answer parcel ── “here you go” ── and sends it back.
In other words, this world has a “side that asks” and a “side that answers.” The asking side is your PC or phone ── in technical terms, the client (the one making the request). And the answering side is ── the server (the one that serves).
1-2. Behind the Counter, There Is a Headquarters That Keeps the Records
Let’s bring this closer to everyday experience. The browser or app you touch directly is, so to speak, the counter in front of you. The counter accepts your requests, but the business is not completed at the counter alone. All the records ── the site itself, the member ledger, the product data ── are stored and managed at a headquarters, which always sits somewhere far away. The counter contacts the headquarters on your behalf and displays the returned answer on your screen.
The computer playing that headquarters role is the server. When our past articles spoke of “the side holding the ledger” (→ our cookie article) or “the side holding the original materials” (→ our cache article), they were all talking about this headquarters.
The counter in front of you, and the faraway headquarters You ──"Please give me this page"──> Headquarters (server) △ ・stores the site itself and the ledgers the counter ・answers requests 24 hours a day (browser / app) You <──"Here you go"───────────── Headquarters (server) the side that asks = client (your PC / phone) the side that answers = server (the faraway source)
1-3. “Server” Is the Name of a Role, Not of a Machine
Here is the single most important sentence of this article: “server” is not the name of a kind of machine, but the name of a role. Whatever carries out the job of “answering when asked” is a server.
As proof: the ordinary PC in front of you can become a server the moment you run the dedicated software on it. In fact, web developers routinely spin up a practice server that runs only inside their own PC to test their sites (a mechanism called localhost ── a topic that deserves an article of its own). Conversely, no matter how expensive and large a machine is, if it answers nobody’s requests, it is just a computer.
2. How It Differs from Your PC ── Not the Specs, but the Way It Works
2-1. “For You Alone” vs. “For the Whole World”
If an ordinary PC can be a server, why do dedicated machines exist? The decisive difference is not performance but the way they work.
Your PC works “for you alone, only while you’re using it.” You may switch it off at night, and you can reboot it whenever you like. The server ── the headquarters ── on the other hand, keeps answering “for an unspecified crowd all over the world, 24 hours a day, 365 days a year.” Since nobody knows when the next request will come, it is never allowed to sleep.
How your PC and a server work differently Your PC serves : you alone runs : only while in use (may sleep at night) if it stops : one person is inconvenienced ── you Server (headquarters) serves : an unspecified crowd, worldwide runs : 24 hours a day, 365 days a year if it stops : every user is affected (= "the server is down")
2-2. What “24 Hours, for Anyone” Demands
This difference in the way of working translates directly into a difference in equipment.
| Requirement | Ordinary PC | Server machine |
|---|---|---|
| Never stopping | If it crashes, just reboot | Power and parts are duplicated so a failure doesn’t stop it |
| Handling many requests at once | Basically one user | Designed for thousands to tens of thousands of simultaneous accesses |
| Where it lives | On a desk | A data center ── a dedicated building with cooling, backup power, and thick network lines |
2-3. That’s Why They Look Different, Too
Server machines often come without a screen or keyboard because they are not machines for a person to use directly, but machines that answer requests over the network. The data-center photos you’ve seen ── shelves packed tight with PCs connected by a maze of cables ── show a headquarters that has gathered a huge number of answering clerks.
The idea that “a server = a high-spec PC” gets the order backwards. The role comes first ── answering an unspecified crowd 24 hours a day ── and the machine ends up sturdy and powerful in order to endure it. Performance is not what defines a server.
3. Kinds of Servers ── Just the Name of the Job They’re Asked to Do
3-1. The Naming Is Simple
Web servers, mail servers, DNS servers ── the variety looks endless, but the naming rule is simple: “what it gets asked to do” is stuck on the front, and that’s all. The one that answers “please give me this web page” is a web server; the one that holds your mail and delivers it is a mail server.
3-2. The Main Kinds of Servers
| Name | The job it’s asked to do | Related article on this site |
|---|---|---|
| Web server | Answers “please give me this page” by returning the full set of page materials | The star of this article |
| Mail server | Holds your mail, passes it to the recipient’s mail server, and stores it in the inbox | ── |
| DNS server | Answers lookups like “what’s this site’s address (IP address)?” | The keeper of the “phone book” in What is DNS? |
| File server | Stores the contents of the office shared folder and hands them to whoever opens them | ── |
| Game server | Tallies opponents’ positions and results and keeps everyone’s screens in sync | ── |
You see “the server is down” in games and on ticket sites alike because behind every service, there is a headquarters of its own.
3-3. One Machine Can Play Many Roles ── and Hundreds Can Share One
Server being the name of a role also settles the question of machine counts. On a small site, it is perfectly common for one machine to double as both the web server and the mail server (inside the headquarters, the clerks are told apart by “reception numbers” ── a mechanism called port numbers, another topic that deserves an article of its own). Conversely, in large services, the single role of web server is shared by hundreds of machines. Roles and machines are not one-to-one.
There is also a mechanism that scatters warehouses holding copies of the materials around the world and answers from the nearest one (a CDN). It is the true identity of the “delivery network’s warehouses” introduced in our cache article ── and yet another topic that deserves an article of its own.
4. What “the Server Is Down” Really Means ── the Source Can No Longer Answer
4-1. “Down” Means the Headquarters Can No Longer Answer
With the picture built so far, “the server is down” can be explained in one line: the headquarters can no longer answer requests. Your counter (the browser) may be perfectly fine ── but if the headquarters it contacts stays silent, no counter anywhere can get the business done. The causes fall into three broad groups.
| Cause | What is happening | Typical scene |
|---|---|---|
| ① Congestion | Requests flood in at once and processing can’t keep up | “Slow” and “can’t connect” right after tickets go on sale or a popular game updates |
| ② Failure | A hardware or software fault stops the answering | Even with duplicated parts, it happens when it happens |
| ③ Maintenance | Deliberately stopped, on a schedule, for updates and checks | The “under maintenance until X o’clock” notice |
What happens at the headquarters when congestion takes it "down"
Normally:
request ─────────> [reception] ──> an answer comes right back
Congested:
request request request request ──> [reception] ── can't keep up
△ the queue grows, answers slow down,
and eventually it becomes "cannot answer"
4-2. Is It Your Side or Theirs? ── the Order to Check
When you “can’t connect,” you can tell whether the cause is your line or their headquarters by checking in this order.
- 1Open another siteIf others open normally, your line is fine ── suspect that site’s headquarters.
- 2Try another lineSwitch off Wi-Fi and try mobile data. Still failing? Then it’s almost certainly their side.
- 3Look for outage reportsIf the operator has posted a notice, or social media is full of “can’t connect,” that settles it.
Once you know the headquarters is the cause, the only thing you can do is wait. Hammering the reload button actually piles extra requests onto an already congested headquarters and drags out the recovery.
And here is how to tell this apart from the symptom covered in the cache article ── if an old page is displayed, suspect your local warehouse (the cache); if you can’t connect at all or get errors, suspect the headquarters. What the trouble looks like tells you where to look.
5. Where Are Servers, Anyway? ── Buy, Rent, or Rent Just What You Need
5-1. Three Ways to Set Up a Headquarters
Seen from the side that builds a site or service, there are three main ways to set up the headquarters.
| Setup | What it means | Suits |
|---|---|---|
| Own it | Buy the machines and run them in your own machine room (called on-premises) | Large companies, special requirements |
| Rent it | Rent a slice of a machine in a data center for a monthly fee ── a rental server | The classic choice for personal and small-to-mid sites |
| Rent just what you need | Rent capacity only for as long as needed and pay for what you use ── the cloud | Services whose scale grows and shrinks |
“Signing up for a rental server” doesn’t mean buying a machine ── it means renting a seat at a headquarters that keeps answering 24 hours a day. The cloud makes that renting even more flexible, and it too deserves an article of its own.
5-2. Whatever the Setup, the Role Stays the Same
Owned, rented, or cloud ── what it does is the same: record and keep the information, and answer requests 24 hours a day. Only the location and the rental terms differ; “being in the cloud” doesn’t make anything magical happen. Even as an individual, rent a server and you can have your own site’s headquarters starting today.
Summary ── the 4-Line Essence
- “Server” is the name of a role: the clerk that records and keeps the information and “answers when asked” ── not a kind of machine, so an ordinary PC can be one, and one machine can play several roles
- The difference from your PC is the way it works: a machine at hand that runs for one person only while in use, versus a headquarters that answers an unspecified crowd 24 hours a day ── the performance gap is merely a consequence of the role
- The kinds are just named after the job: web, mail, DNS, file, game ── behind every service, there is a headquarters of its own
- “Down” means the headquarters can’t answer: the causes are congestion, failure, or maintenance ── and if it’s their side, the only thing you can do is wait
With this, the story of the counter in front of you (the browser trilogy: HTTPS, cookies, and cache) and the story of the faraway headquarters (this article) are both in place. To reread the whole journey a request travels → the series overview.
FAQ
Q1. What is the difference between a server and an ordinary PC, in the end?
A. Before any difference in hardware, there is a difference in the way they work. An ordinary PC runs “for you alone, only while you’re using it”; a server keeps answering “for an unspecified crowd, 24 hours a day.” To endure that role, differences in hardware follow ── duplicated parts, designs for massive simultaneous access. It’s not a server because it’s powerful; it’s a server because it carries the role of answering.
Q2. What state is “the server is down”? Is waiting really all I can do?
A. It’s the state where the answering side (the headquarters) can no longer answer. The causes fall into congestion, failure, and maintenance (→ §4). To narrow it down, check in this order: do other sites open → does another line fail too → are there outage reports. If the headquarters is the cause, waiting is all a user can do. Hold off on hammering reload ── it makes the congestion worse.
Q3. Can I turn my own PC into a server?
A. Yes. Since “server” is the name of a role, an ordinary PC becomes the answering side once you install the dedicated software. The practice server developers run entirely inside their own PC (localhost) is the classic example. But to use it as a real public server, you’d need to keep it powered on 24 hours a day and handle the security work of fending off outside attacks ── so for actually going public, a rental server or the cloud is the realistic choice.
Q4. What’s the difference between a rental server and the cloud?
A. Both are still “renting a seat at the headquarters”; what differs is how you rent. A rental server is a fixed seat for a monthly fee ── predictable pricing, the classic choice for personal sites. The cloud rents capacity only for as long as needed and bills for what you use ── suited to services whose traffic swings sharply. The detailed trade-offs deserve an article of their own, planned for the future.
Q5. Does the server side have caches and cookies too?
A. It does. Each mechanism from the browser trilogy has a partner on the headquarters side. The ledger against which cookie membership cards are checked is kept at the headquarters (→ our cookie article), and the original materials live at the headquarters too, with spare warehouses on the headquarters side and in the delivery network (CDN) (→ our cache article §2). The counter in front of you and the faraway headquarters hold up the same mechanisms from both ends.
Leave a Reply