What It Actually Means
Amazon Web Services, Google Cloud and Microsoft Azure are the large ones. There are smaller providers offering a similar model with considerably less complexity.
The distinction from traditional hosting is elasticity. A conventional server is a fixed thing you rent monthly whether you use it or not. Cloud capacity can expand for an hour and contract again.
What It Actually Solves
Variable load. If your traffic is ten times higher on Monday morning, paying for Monday capacity all week is waste. This is the case cloud was designed for.
Not owning hardware. No machines to buy, replace or house.
Geographic reach. Running close to users in several countries.
Services rather than servers. Managed databases, storage, queues and email, so you are not maintaining that software yourself. For small teams this is frequently the biggest practical benefit and it gets less attention than it deserves.
What It Costs, Honestly
For a steady, modest system, cloud hosting is often more expensive than a straightforward virtual server, sometimes substantially.
The elastic pricing that saves money on spiky workloads costs money on flat ones, and the bill is composed of many small charges that are difficult to predict: compute, storage, data transfer, requests, load balancing, backups, each metered separately.
The charge that surprises people most is data transfer out. It is cheap per unit and adds up on anything media-heavy, and it appears in no comparison anyone does beforehand.
There is also a complexity cost. The large platforms are genuinely complicated, and configuring them properly is a skill. A business without that skill in-house either pays for it or ends up with something misconfigured, and misconfiguration is where both surprise bills and security exposures come from.
The Honest Recommendation
Match the hosting to the actual shape of the workload.
A brochure site or a small business application with steady traffic runs perfectly well on managed hosting or a modest virtual server, for a predictable monthly figure, with far less to go wrong.
Genuinely variable load, or a requirement for managed services justifies cloud, and the smaller providers deliver most of the benefit with a fraction of the complexity.
Large scale or specific compliance requirements is where the major platforms earn their cost.
Choosing the largest platform for a small steady system is a common and expensive default, usually chosen because it sounds like the professional answer.
What To Ask
- What is our actual traffic pattern? Flat or spiky. This decides everything.
- What is the monthly cost, and what makes it vary? Ask which charges are unpredictable.
- Who configures and maintains this? If nobody in-house understands it, that is a real ongoing cost.
- What are we using that we could not get from a simpler arrangement? If nothing, the complexity is unpaid for.
- Is there a spending alert? Cloud bills can rise sharply through misconfiguration or a loop, and the first warning should not be the invoice.
More terms are in the glossary.
