Where software actually runs — the hosting models, cloud layers and infrastructure vocabulary behind every website you've ever loaded.
Every digital project eventually answers the same unglamorous question: what machine serves this, and who keeps it alive? The answers form a ladder — from shared hosting through VPS and dedicated machines to the cloud's rungs of abstraction (IaaS, PaaS, serverless) — plus the delivery chain that stands in front of all of them: domains, DNS, TLS, caching and CDNs. The concepts below map that territory; each one states plainly what a model gives you, what it quietly hands back to you, and when the next rung is worth its price.
Shared hosting places many customers' websites on one server that pools its processor, memory and disk between them, which makes it the cheapest way to put a site online — and the reason a busy neighbor can slow yours down.
A VPS is a software-defined slice of a physical server that behaves like a machine of its own — reserved CPU, memory and disk plus full administrative access — so you get root without paying for the whole box.
A dedicated server is an entire physical machine rented by one customer — no hypervisor, no co-tenants — chosen when raw performance, hardware-level control or strict isolation matters more than the flexibility of virtual machines.
Managed hosting is any hosting arrangement where the provider operates the server for you — updates, security, monitoring, backups and tuning — so what you are really buying is ops expertise attached to infrastructure, not the infrastructure itself.
Cloud hosting provisions computing resources — virtual machines, storage, databases — on demand through an API from a provider's pooled infrastructure, billed by usage rather than by rented box.
A web server is the program that listens for HTTP requests and answers them — serving files directly or passing the request to application code — with nginx and Apache as the long-standing workhorses of the role.
IaaS is the rawest cloud offering: virtual machines, storage volumes and networks rented as building blocks through an API, with everything above the infrastructure — operating system, runtime, application — assembled and operated by you.
PaaS is a cloud layer where you hand over code and the platform does the rest — provisioning, runtimes, scaling and deployment — trading infrastructure control for development speed.
Serverless computing runs code on demand without any server you rent or manage: functions execute when an event triggers them, scale to zero between requests, and bill by actual execution rather than reserved capacity.
A container packages an application together with its runtime environment — libraries, dependencies, configuration — into one portable unit that runs identically wherever a container engine exists, isolated by the host kernel rather than by a virtual machine.
Object storage keeps files as self-contained objects in flat buckets addressed over HTTP — no file system, no attached disk — scaling to practically unlimited size and billed by what you store and transfer.
Load balancing distributes incoming requests across multiple servers so that no single machine carries the traffic alone — the mechanism that turns 'add more servers' into an actual scaling strategy and single-server failure into a non-event.
A CDN is a network of servers spread across the world that keeps copies of your site's content close to visitors, so requests are answered from a nearby edge location instead of traveling to your origin server.
DNS is the internet's address book: the distributed system that translates human-readable domain names into the machine addresses and service pointers that actually route traffic — and the control panel where a domain's fate is decided.
TLS (still widely called SSL) is the protocol that encrypts traffic between browser and server and proves, via certificates, that the server really speaks for its domain — the mechanism behind the padlock and the S in HTTPS.
A domain name is a rented address in the internet's namespace — registered through a registrar for annual fees, controlled entirely by whoever holds the registrar account, and independent of wherever the website behind it happens to be hosted.
Caching stores the result of expensive work — a rendered page, a database query, a downloaded file — and serves the stored copy while it is still valid, trading a little freshness for most of a system's speed.
Uptime measures the share of time a service is reachable, quoted in 'nines'; an SLA (service level agreement) is the contract clause that defines how that share is counted and what compensation — usually service credit — a miss triggers.
