The Missing Manual
⌘K
← Back to guide / Phase 0
Updated Jun 19, 2026

Inside a Server & Data-Center Hardware

You've deployed to "a server." You've spun up a "cloud instance." You've heard a thousand times that "the cloud is just someone else's computer" - and nodded, without ever being shown whose computer, what it looks like, or why it's built the way it is. This guide opens the box. We'll start with one physical machine - the same fundamental parts as the laptop in front of you, arranged around a completely different set of priorities - and zoom out, rack by rack, until you can picture the literal building your code runs in.

This is a hardware guide, not an admin guide. We're not going to SSH in and configure anything. We're going to look at the metal: what it is, why it's shaped that way, and what changes when a machine's job is to never, ever stop. If you already operate Linux servers, this fills in the picture underneath the shell - and when you're ready to actually drive one, Linux for Servers picks up exactly where this leaves off.

How to read this

  • Just want the punchline on "the cloud"? Jump to Phase 3: The Data Center & "The Cloud"
    • but the payoff lands harder if you've met a single server first.
  • Want it to finally make sense? Read in order. Each phase zooms out one level: one machine, then how one machine is made reliable, then a building full of them.

The phases

  1. A Server vs Your Laptop - same fundamental parts (CPU, RAM, storage), arranged around different priorities: rack-mount form factor, ECC memory, more cores and sockets, redundant power, and remote management for a machine with no monitor.
  2. Built Not to Stop - Redundancy & Reliability - the reliability mindset in hardware: RAID, hot-swap drives and power supplies, and the single principle underneath it all - eliminate the single point of failure. (Including the line that has saved a lot of careers: RAID is not a backup.)
  3. The Data Center & "The Cloud" - zoom all the way out: rows of racks, top-of-rack networking, power and cooling, redundancy at building scale - and then a precise, demystified answer to what a cloud VM actually is.

This guide stays at the hardware level. What you do with a server once you can reach it - SSH, services, logs, security - lives in Linux for Servers. The deeper electronics of CPUs, RAM, and storage have their own homes too: How a Computer Works, CPU, RAM & Storage, and Storage: HDD, SSD & NVMe.