Cloud Computing
What cloud computing is, how the main service and deployment models differ, where your data actually lives, and what to watch for on cost and security.

Cloud computing is the on-demand delivery of computing resources over the internet, with pay as you go pricing. Instead of buying and maintaining your own servers, you rent computing power, storage, databases and software from a provider such as Amazon Web Services (AWS), Microsoft Azure or Google Cloud, and you use only what you need.
Think of it like electricity. You do not build a power station to run your home. You connect to the grid, use what you use, and pay for that. The cloud does the same for computing.
What you actually get from the cloud
Most cloud services fall into a few everyday groups:
- Compute: Virtual servers and functions that run your code.
- Storage: Space for files, photos, backups and app data.
- Databases: Managed databases, so you store and query data without running a database server yourself.
- Networking: The connections, load balancers and content delivery that let people reach your app.
- Software: Complete applications delivered over the internet, such as email, file sharing and customer tools.
You access all of this through the internet, usually from a web console, an app or code, and you can start or stop most of it in minutes.
The three service models
Cloud services are grouped by how much the provider runs for you and how much you run yourself.
| Model | Provider runs | You run | Common example |
|---|---|---|---|
| IaaS | Hardware and networking | Operating system and apps | A virtual server you configure yourself |
| PaaS | Hardware, networking and platform | Your code and data | A managed platform that hosts your app |
| SaaS | Everything, including the app | Settings and your data | Email, file storage or accounting software |
IaaS stands for Infrastructure as a Service, PaaS stands for Platform as a Service, and SaaS stands for Software as a Service.
In simple terms: with IaaS you rent the building blocks and build the rest, with PaaS you bring the code and the provider runs the platform under it, and with SaaS you just use the finished product. Most people use SaaS every day without calling it cloud computing.
Public, private and hybrid cloud
These terms describe where the cloud runs and who it is for.
- Public cloud: You share the provider's infrastructure with other customers, with your data kept separate by their controls. This is the most common option, and usually the cheapest place to start.
- Private cloud: Cloud style infrastructure run for one organisation only, in its own data centre or a dedicated one. It gives more control, at a higher cost.
- Hybrid cloud: A mix of the two. Some systems stay on your own infrastructure and some move to the public cloud, and they work together.
Many organisations end up hybrid, not by plan but by stages: new projects start in the public cloud, older systems stay where they are, and the two connect.
Common uses
- Hosting websites and apps that need to handle quiet days and busy days with the same setup.
- Storing files and photos, and sharing them across devices.
- Backing up data and recovering it after a failure, without keeping a second site of your own.
- Testing software in an environment you can create, use and delete in a day.
- Working with large amounts of data, analytics and AI tools that would be expensive to set up on your own hardware.
- Using ready made software for email, documents, meetings and business tasks.
Why people move to the cloud
- No large upfront cost: You do not buy servers before you know whether a project will work.
- Scale up and down: Add capacity for a busy period, then release it when things go quiet.
- Speed: A new server, database or test environment can be ready in minutes, not weeks.
- Reach: You can place an app closer to users in other countries without opening an office or a data centre there.
- Less maintenance: The provider looks after the physical hardware, the building and much of the patching, depending on the model you choose.
What the cloud does not fix for you
The cloud removes the job of owning servers. It does not remove the need to manage what you use.
- Cost can rise quietly: Pay as you go also means you pay for everything you forget to turn off. Idle servers, unused storage and data moving out of the cloud can make a bill larger than expected.
- Security is shared: The provider secures the infrastructure. You still control who has access, how strong the passwords and keys are, and what you store where. Most cloud security problems come from settings on the customer side.
- You depend on the internet: If your connection goes down, you may not reach your own apps and files.
- Switching providers is work: Each provider has its own tools and services. Using a lot of provider specific services can make a later move slow and expensive. Keeping your data in common formats, such as CSV or standard database exports, helps.
- It is not always cheaper: A steady workload that runs all day, every day, can sometimes cost less on hardware you own. The cloud is strongest where demand changes, or where you want to start without a large purchase.
Where is the cloud actually located?
There is nothing floating in the sky. The name comes from old network diagrams, where the internet was drawn as a cloud shape to show a network you did not need to draw in detail. The services themselves run in real buildings.
Every file and app sits on a physical server, in a data centre, in a specific place.
Providers organise those data centres in two levels:
- A region is a geographic area, such as a region in Canada, the United States or Europe. You choose the region, and your data stays there unless you move or copy it.
- An availability zone is one or more data centres inside a region, kept separate from the others so a problem in one does not take down the rest.
Where you choose matters for three simple reasons:
- Speed: An app is faster for users when it runs in a region close to them.
- Reliability: Spreading an app across availability zones keeps it running if one data centre has a failure.
- Rules about data: Some types of data have rules about which country they can be stored or processed in. Check that before you pick a region, not after.
Checklist before you start
- Name what you want to run or store, and why the cloud helps with that specific thing.
- Start with SaaS if a ready made product does the job, and PaaS or IaaS only if you need more control.
- Pick a region close to your users, and check any rules about where the data can live.
- Set up access properly from day one: separate accounts, strong passwords and multi factor authentication.
- Set a budget alert, and turn off test resources when you are done with them.
- Keep a copy of important data in a format you can take with you.
What to try next
Pick one small, low risk project. Host a simple website, move a set of files to cloud storage, or try a managed database for a side project. Use it for a week, look at what it cost, and note what was easier and what was not.
That small test will show you more about cloud computing than any definition: what you control, what the provider controls, and what you actually pay for.
About the author
- I am an Engineer in love with software and writing code. I am super passionate about the reach of technology, and when it comes to conquering new frontiers, I want to be there in the forefront.



