The Ultimate Glossary of Server and Hosting Terms

Every hosting setup guide assumes you already know what a reverse proxy is, what TTL controls, and why your host keeps mentioning PHP-FPM pools. Most of these terms take one sentence to explain properly, and nobody bothers — you're left piecing together meaning from context, half-remembered forum posts, and whatever the error message happened to say. This glossary covers the ones you will actually run into while managing a server, grouped by where you would meet them: infrastructure, the web server layer, networking, security, and the database and automation tools running underneath everything. No filler definitions, no jargon explaining jargon — just what each term means and why it matters the first time you hit it.

Infrastructure Basics

VPS (Virtual Private Server) is a slice of a physical machine, virtualized to give you dedicated CPU, RAM, and disk allocations along with root access — isolated from the other tenants running on the same underlying hardware. It's the default building block for most modern web hosting because it's cheap, scriptable, and disposable — you can provision one in minutes and destroy it just as fast when it's no longer needed.

A Dedicated Server is an entire physical machine leased to one customer, with nobody else's workload sharing its resources. You reach for one when you need guaranteed hardware, strict compliance isolation, or performance that a shared or virtualized environment can't promise.

A Load Balancer sits in front of multiple servers and distributes incoming traffic across them, usually based on round robin, least connections, or active health checks. It means no single server absorbs the full load, and one server going down doesn't take the whole app offline.

Swap is disk space configured to act as overflow memory once a server's physical RAM is exhausted. It stops an out-of-memory process from crashing outright, but at the cost of speed — disk is orders of magnitude slower than RAM, so a server that's actively swapping is a server that's struggling, and heavy swap usage is usually a sign you need more RAM, not more swap.

Web Server & PHP

Nginx is a web server and reverse proxy built around an event-driven, non-blocking architecture, which lets it handle a large number of concurrent connections efficiently. It's commonly used to serve static files directly and hand off dynamic requests to a backend process.

Apache is the other major web server, using a process- or thread-per-connection model with deep support for per-directory .htaccess configuration. It's still widely used, particularly on stacks that depend on legacy .htaccess rewrite rules, and it's common to see Nginx and Apache run together, with Nginx handling static content and proxying dynamic requests back to Apache.

PHP-FPM (FastCGI Process Manager) is the daemon that manages pools of PHP worker processes, so Nginx or Apache can hand off a PHP request to be executed without spawning a fresh interpreter each time. Each site typically runs its own pool with its own PHP version and memory limits.

A Reverse Proxy sits between clients and one or more backend servers, forwarding requests on their behalf. It's used to terminate SSL, cache responses, load balance, or simply hide the backend's real address and port from the outside world — Nginx sitting in front of a Node.js app on port 3000 is a reverse proxy in practice, and it's why you'll see that pattern in nearly every non-PHP deployment.

Networking & DNS

DNS (Domain Name System) translates human-readable domain names into IP addresses — it's the internet's phone book, and every request to a domain starts with a DNS lookup before any connection is even opened. DNS is also hierarchical and cached at multiple layers, which is exactly why changes don't take effect instantly everywhere at once.

An A Record is a DNS record type that maps a domain name directly to an IPv4 address. It's the record you edit when pointing example.com at your server's IP for the first time.

TTL (Time To Live) is how long a DNS resolver is allowed to cache a record before it has to ask again. A lower TTL propagates changes faster but generates more DNS query traffic; a higher TTL is more efficient but means a mistake takes longer to fully undo.

A CDN (Content Delivery Network) is a distributed set of edge servers that cache and serve your static assets from a location physically close to the visitor, instead of round-tripping to your origin server for every request. It cuts latency and offloads bandwidth your origin would otherwise carry, which matters most for image-heavy sites and visitors far from your server's region.

Security & Access

SSL/TLS — SSL (Secure Sockets Layer) is the deprecated predecessor to TLS (Transport Layer Security), the protocol that actually encrypts traffic between a browser and your server today. "SSL certificate" stuck around as the common phrase, but virtually every connection is negotiated over TLS now.

A Firewall filters inbound and outbound traffic by port, protocol, and IP address, and it's one of the first things you should configure on any freshly provisioned server. CSF (ConfigServer Security & Firewall) is a popular Linux firewall front end built on top of iptables that adds login failure detection and automatic IP blocking on top of basic rule filtering.

SSH (Secure Shell) is the encrypted protocol used to log into a remote server's command line, run commands, transfer files, or tunnel other traffic securely. It's how you actually get onto a VPS to do anything at all.

sudo lets a permitted user run a single command with root privileges without switching to the root account outright. It's the standard way to perform administrative tasks on Ubuntu and Debian servers while keeping a record of who ran what.

Databases & Automation

MySQL/MariaDB — MySQL is the original relational database most PHP applications, including WordPress, are built against. MariaDB is a community-developed fork created after Oracle acquired MySQL, and it's drop-in compatible for nearly all standard queries — most modern hosting stacks default to it now, and switching between the two rarely requires changing a single line of application code.

A Cron Job is a scheduled task that Linux's cron daemon runs automatically at defined intervals — used for backups, cache clearing, WordPress wp-cron alternatives, and anything else that needs to happen on a timer without a human triggering it.

systemd is the init system and service manager on modern Linux distributions. It's what starts, stops, restarts, and sequences services like Nginx or MySQL, and it's what brings the whole system up in the right order at boot. Checking whether a service is actually running comes down to one command:

Putting It Together

None of these terms are complicated on their own — the confusion comes from meeting five of them at once in a single error message or setup guide. Bookmark this page, and the next time a host mentions a PHP-FPM pool timing out, a TTL that hasn't expired yet, or a load balancer health check failing, you'll know exactly which layer of the stack is talking to you. Understanding the vocabulary doesn't replace hands-on experience, but it does mean you'll stop treating server management as a black box and start recognizing the same handful of moving parts showing up again and again under different names.