Understanding the Cloud: What You Actually Rent
The cloud is not magic and it is not someone else's computer in the vague sense. Here is what you are really buying, and the bill traps to expect.
The word "cloud" hides a simple fact: you are renting computers, disks and network connections that belong to someone else. Everything surprising about cloud costs comes from forgetting that you are renting by use.
The three things you rent
Almost every cloud service is one of these, or a managed combination of them.
- Compute. A virtual machine, or a container, or a function that runs only when triggered. You pay for time, memory and sometimes for requests.
- Storage. Object storage for files, block storage for disks attached to a machine, and managed databases for structured data.
- Network. Traffic moving in is usually cheap or free; traffic moving out is charged, and this is the line item that surprises people.
Managed services add convenience on top: someone else handles backups, patching and scaling for a premium.
The service models
| Model | You manage | Provider manages | Typical use |
|---|---|---|---|
| Virtual machine | OS, runtime, app | Hardware, network, hypervisor | Full control, legacy apps |
| Containers | App and its dependencies | OS, orchestration | Most modern web services |
| Serverless functions | One function | Everything else | Spiky or light workloads |
| Managed database | Data and queries | Backups, replication, patching | Almost every product |
The trade is always the same: less to operate, less to control, and a price that scales with usage instead of being fixed.
Where the bills come from
Cloud cost problems are rarely about the headline price of a server. They come from these:
- Egress. Serving files or video to users is charged per gigabyte in most providers, and it can dwarf compute.
- Idle resources. A forgotten test server or unattached disk bills every hour, forever.
- Over-provisioning. Choosing a large instance "to be safe" multiplies the monthly number for capacity you never use.
- Logs and monitoring. High-cardinality metrics and long retention generate real, invisible cost.
- Requests. Serverless is cheap per call until a loop or a bot turns millions of calls into a real bill.
The defence is unglamorous: budgets and alerts set before launch, tags on everything, and a monthly review of what is actually running.
How to choose a model
Work backwards from the workload.
- Steady traffic, predictable load. A small virtual machine or container is often the cheapest and simplest.
- Very spiky or rare traffic. Serverless means you pay almost nothing while idle.
- Static site or media. Object storage plus a CDN is dramatically cheaper than serving from a server.
- Anything with a database. Use a managed one, at least at first; running your own database is a specialism, not a shortcut.
The habits that keep it sane
- Start small and measure. Scale up when a metric says you must, not because a blog post recommended a size.
- Automate the environment. Infrastructure defined in files can be reviewed, recreated and deleted cleanly.
- Set a spending alert on day one. The cheapest possible insurance.
- Delete ruthlessly. Unused resources are the most common cause of a bill that "makes no sense".
- Keep an exit in mind. Prefer portable technologies unless a managed service earns its lock-in through real savings.
The bottom line
The cloud rents you compute, storage and network by the meter. Choose the smallest model that fits the workload, watch egress and idle resources, and set alerts before you need them.
