Mirco Cloud Primer
Photo by Gije Cho on Pexels
If you have ever streamed a video, saved a photo to an online account, or used software that opens in a browser instead of installing on your computer, you have already used cloud computing. The word "cloud" sounds abstract, but the idea behind it is simple: instead of buying, owning, and maintaining your own computers, you rent computing power, storage, or finished software from a company that already has the equipment running.
This article breaks down the official definition of cloud computing in plain language, explains why the term confuses so many beginners, and shows how the pieces fit together.
The short definition
The U.S. National Institute of Standards and Technology (NIST) publishes a widely used definition of cloud computing. Stripped of jargon, it describes cloud computing as a way of getting computing resources — processing power, storage, networking, or ready-to-use software — over the internet, on demand, without having to buy or manage the physical equipment yourself.
Five ideas sit underneath that definition, and NIST names all of them: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. You do not need to memorize those terms, but understanding what they mean in practice makes the rest of this library much easier to follow.
Renting instead of owning
A useful comparison is housing. Owning a house means you are responsible for the roof, the plumbing, and every repair, but you also have full control and no landlord. Renting an apartment means someone else owns and maintains the building, and you simply use the space you need, paying for the time you use it.
Traditional computing is like owning a house: a business buys servers, installs them in a room, and someone on staff has to keep them running, updated, and secure. Cloud computing is like renting: a provider owns large facilities full of servers, and you use a slice of that capacity through the internet, paying only for what you actually use.
What actually changes behind the scenes
When you use a cloud service, your request travels over the internet to a facility called a data center, which is really just a very large, carefully managed building full of servers, cooling systems, and backup power. Software inside that data center decides which physical machine handles your request, often splitting one powerful computer into many smaller virtual ones so multiple customers can share it safely — a concept explored in more depth in our articles on the shared responsibility model and in the Compute, Containers and Serverless category.
None of that complexity is something you normally have to think about. The entire point of cloud computing is that the provider absorbs the complexity of buying, housing, cooling, and maintaining hardware, while you focus on using the result.
Why the term causes so much confusion
Part of the confusion comes from marketing. Over the years, companies have attached the word "cloud" to almost anything that involves the internet, which waters down the term. Another part comes from the word itself: "cloud" suggests something intangible, when in reality every cloud service runs on very real, very physical hardware somewhere on Earth.
It also does not help that cloud computing is not one single thing. It includes renting raw computing power, renting a ready-made platform to build on, and renting finished software you simply log into. Those differences matter enough that they get their own dedicated explanations elsewhere in this library, particularly in the Service and Deployment Models category.
A simple way to recognize cloud computing
You can usually tell you are dealing with cloud computing if most of these are true:
- You access it over the internet rather than installing it entirely on your own machine.
- You can get more of it (more storage, more processing power) almost immediately, without buying new hardware.
- You are billed based on how much you use, rather than a single large upfront purchase.
- Someone else is responsible for keeping the underlying machines running and updated.
Common mistakes beginners make
Beginners run into a handful of predictable misunderstandings:
- Assuming "the cloud" is a single company or a single physical place, when it actually describes a model that many different providers offer.
- Believing that moving something to the cloud automatically makes it more secure or more reliable, when security still depends heavily on how the service is configured.
- Confusing cloud computing with simply having an internet connection, rather than understanding it as a way of delivering computing resources.
- Thinking everything in the cloud is infinitely scalable with zero planning, when real limits and real configuration choices still apply.
Frequently asked questions
Is the cloud just someone else's computer?
In a physical sense, yes — your data and programs run on hardware owned by a provider. But the cloud also adds software that makes that hardware behave like an on-demand, shared utility, which is the part that makes it genuinely different from simply renting one computer.
Do I need to understand networking to use cloud computing?
No. Most cloud services are designed so you interact through a website, an app, or a simple dashboard. The underlying networking is real, but providers hide most of it from everyday users.
Is cloud computing the same as the internet?
No. The internet is the network that connects you to cloud services, but cloud computing specifically refers to renting computing power, storage, or software that runs on someone else's infrastructure.
Can a business have its own private cloud instead of using a public one?
Yes. Some organizations build cloud-style, on-demand systems on their own hardware. That approach is usually called private cloud, and it follows the same core ideas as public cloud computing.
Related reading
Sources
- NIST Special Publication 800-145 — The NIST Definition of Cloud Computing
- Documentation published by major public cloud providers (consulted October 2026)