What is cloud computing? It is the practice of renting computing power, storage, and software from someone else’s building, delivered over a network, billed by the minute or the gigabyte. The cloud is not floating and it is not abstract. It is a warehouse full of servers in a place with cheap electricity and good fiber.
The name survives because it hides the important part: you no longer own the machine, and you no longer have to guess how much machine you will need next year.
Nobody’s Data Is in the Sky
When you upload a photo to a cloud service, it lands on a disk in a data center, probably in a cluster of buildings in northern Virginia, central Oregon, or Dublin. Those regions were chosen for power, land, and tax reasons, not for weather.
A large facility draws tens of megawatts and consumes millions of gallons of water a year for cooling. That physical footprint is why cloud providers care so much about efficiency: a few percent saved on cooling is a large number of dollars.
The Three Layers
| Model | What you rent | What you manage | Example |
|---|---|---|---|
| IaaS | Virtual machines, disks, networks | Operating system, runtime, app | Renting a Linux server |
| PaaS | A runtime that runs your code | Only the application | Managed app hosting |
| SaaS | A finished application | Only your data and settings | Web-based email |
| Serverless | Execution per request | Only the function | Image resizing on upload |
The layers trade control for convenience. IaaS gives you a machine that behaves like hardware you own, including the obligation to patch it. SaaS gives you nothing to patch and nothing to tune.
Virtualization Is the Trick
A hypervisor divides one physical server into many virtual machines, each convinced it has its own processor, memory, and disk. Because most servers sit idle most of the time, this packing raises utilization from perhaps 15 percent to well above 50 percent.
Containers go further: they share the host operating system and isolate only the application, which makes them start in milliseconds instead of minutes. That is why modern deployments are usually a pile of containers behind a load balancer rather than a few hand-configured servers.
Regions and the Speed of Light
Distance is not free. Light in fiber travels at roughly 200,000 km per second, so a round trip between New York and London — about 5,600 km each way — cannot beat roughly 56 milliseconds, before any routing, queuing, or processing.
Real measurements land in the 70 to 90 millisecond range. That gap is why “just put it in the cloud” is bad advice for a trading system, a live control loop, or anything that needs a response in under 10 milliseconds.
The Bill Is a Design Decision
Cloud pricing rewards elastic workloads and punishes steady ones. Three patterns cause most of the surprise:
- Egress. Moving data in is often free; moving it out is metered. An architecture that copies a large dataset between regions every hour pays for it every hour.
- Idle capacity. A forgotten development server still bills. So does an unattached disk.
- Storage tiers. Rarely read data belongs in an archive tier at a fraction of the price, but only if someone remembers to move it.
None of these is a trick. They are the natural consequence of metering, and they reward teams that look at the invoice as an engineering artifact.
What Cloud Is Genuinely Bad At
A steady, predictable workload — a database that has run at 40 percent capacity for three years — is often cheaper on hardware you own, once you account for reserved-instance discounts and staff time. The cloud wins on variability, not on average.
The second problem is lock-in. Managed services are convenient precisely because they are proprietary, and moving a queue, a database, or an identity system to another provider can take a year. The exit cost belongs in the original decision, not in the postmortem.
Why It Won Anyway
Before cloud, a new project began with a purchase order and a six-week wait for a server. Afterwards it began with a credit card and four minutes. Removing that delay changed how software is built far more than any pricing model did.
That is the honest answer to what is cloud computing: a business model built on virtualization, which accidentally made experimentation cheap enough to become the default way software gets made.
Keep Exploring
- What is an API? — how your code talks to those rented machines
- How do computers store data? — what is actually on those disks
- How do search engines work? — a system that could not exist without this scale
