1.1 What the cloud actually is
Describes the cloud landscape as of August 2026
What this is and why it exists
"Someone else's computer" is where the joke ends, not where the definition does. Cloud computing has a real definition — five measurable characteristics — and this lesson gives you the words to explain it to a non-technical person and the honesty to say what it is bad at.
The vocabulary
- On-demand self-service — you get resources by asking a system, not a person, and you get them in minutes.
- Resource pooling — the provider serves many customers from shared hardware, which is what makes the economics work.
- Rapid elasticity — capacity grows and shrinks with your need, in both directions.
- Measured service — everything is metered, and you pay for what the meter read.
- Capital expense (capex) — money spent up front on things you then own, like servers.
- Operating expense (opex) — money spent as you go, like a monthly bill.
The mental model
Electricity. You do not build a power station to light a room; you draw from a shared grid, metered, and the grid absorbs everyone's peaks. The cloud does for computing what the grid did for power — with the same fine print: you depend on someone else's infrastructure, their outages are your outages, and heavy continuous use can cost more than owning the machine would have.
What changed is who carries the capital cost and how fast you can get more. What did not change: hardware still exists, still sits in a building somewhere, still fails — the provider's value is that they handle the failing for you.
The honest list of what cloud is bad at: steady, predictable, heavy workloads you could run cheaper on owned machines; moving large data out (the meter runs on exits); work that must live on-premises by law or by latency; and anything a team deploys without reading the meter.
What you should now be able to explain or do
Explain the five characteristics without notes. Say in one sentence what capex-to-opex means for a small Indian startup. Name two workloads that do not belong in the cloud, and say why.
Check yourself
A friend says the cloud is "someone else's computer". What is missing from that?
The five characteristics — self-service, pooling, elasticity, measured billing, network access. Renting a bare machine from a neighbour has none of those; the definition is the delivery model, not the ownership.
What is the difference between capex and opex, in cloud terms?
Capex is buying servers up front and owning them; opex is paying a metered bill for capacity you used. Cloud converts the first into the second.
Name two things the cloud did NOT change.
Hardware still exists and still fails — someone else now runs it. And badly planned workloads still cost money — the meter makes it visible faster.
When is cloud the wrong answer?
Steady, predictable, heavy loads that owned hardware would run cheaper; data that must stay on-premises by law; and latency budgets a remote data centre cannot meet.
Go deeper
We haven't checked most of these for screen reader use yet.
Back to What the cloud actually is: work through the checklist