The cloud is computing you rent instead of own: servers, storage and databases in someone else's data centre, switched on with an API call and paid for by the hour, the gigabyte or the request. It is how a small team can put an app in front of the whole internet without buying a single machine.
What the cloud actually is
Providers such as AWS, Microsoft Azure and Google Cloud run enormous data centres full of servers, disks and network equipment, and rent it out in pieces. When you ask for a virtual machine, software on their side finds spare capacity, carves out a slice of a physical server and hands it to you, usually within a minute or two. When you delete it, the billing stops.
Three things set this apart from renting a server the old way:
- On demand. You create and delete resources yourself, from a web console, a command-line tool or an API call. There is no purchase order and no wait for hardware to arrive.
- Elastic. You can go from one server to fifty and back again in the same afternoon.
- Metered. You pay for what you use, much like electricity, instead of paying up front for capacity you might never need.
The old line 'the cloud is just other people's computers' is true, and worth remembering. Your data sits on physical disks in a real building, in a region you choose. What you are buying is someone else doing the hardware work, plus the services built on top of it.
Why not buy your own servers?
Running your own hardware means paying up front, guessing how much you will need, and dealing with power, cooling and failed disks yourself. Guess too small and the site falls over on launch day. Guess too big and expensive machines sit idle for years.
The cloud turns that up-front cost into a running cost, and shrinks the guess from 'how many servers will we need in three years?' to 'how many do we need right now?'. For a new app with unknown traffic, that is usually the deciding factor. Owning hardware still wins in some cases, which Cloud vs. on-prem looks at.
Wondering how this was made? How we make these